← previous blocknext block →recent activity
Analyzing
Block #92,173,462
21 transactions · 20 stateful · 2026-08-01 10:03:21 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,173,462 · 21 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
6w07w18w09w112w213w314w416w518w319w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa56e54d0…2d39
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x37abe7da…fc68
0x34b655…2a6f
6 touches
3 conflicts
0x9fac0587…2b71
0x34b655…2a6f
6 touches
3 conflicts
0xfac8b200…2365
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x2385516f…eca5
0x34b655…2a6f
4 touches
1 conflict
0x2dd03fb9…6243
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 0xa56e54d018…f82d39
Audit this contract →
← previous block·next block →recent activity