← previous blocknext block →recent activity
Analyzing
Block #86,711,202
23 transactions · 19 stateful · 2026-07-09 22:17:29 UTC
Parallelism
91/100
Blocked
21%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,711,202 · 23 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w110w012w113w118w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ce93f3d…b70e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0bd95eb4…e562
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x74462c1e…84f3
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
1 conflict on slot 0x7ce93f3d92…42b70e
Audit this contract →
← previous block·next block →recent activity