← previous blocknext block →recent activity
Analyzing
Block #86,630,337
24 transactions · 21 stateful · 2026-07-09 13:16:21 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,630,337 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w09w112w213w215w317w323w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ce93f3d…b70e
0x34b655…2a6f
8 touches
6 conflicts
0xccdc4bad…55ad
0x851145…3f07
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x1941b441…5889
0x34b655…2a6f
4 touches
1 conflict
0x21683d77…4e07
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x8eb0ac6b…a73a
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0x7ce93f3d92…42b70e
Audit this contract →
← previous block·next block →recent activity