← previous blocknext block →recent activity
Analyzing
Block #93,248,282
11 transactions · 11 stateful · 2026-08-05 04:12:02 UTC
Parallelism
45/100
Blocked
64%
Avg conflicts / tx
0.91
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,248,282 · 11 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w28w49w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x1741dbc0…73a7
0x34b655…2a6f
6 touches
3 conflicts
0xce2f0b6e…0e05
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x21280422…0930
0x34b655…2a6f
4 touches
1 conflict
0x27034002…2f27
0x34b655…2a6f
4 touches
1 conflict
0x4faee57c…6ca2
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity