← previous blocknext block →recent activity
Analyzing
Block #86,483,396
13 transactions · 11 stateful · 2026-07-08 20:52:57 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,483,396 · 13 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ee6007b…fd68
0x34b655…2a6f
4 touches
1 conflict
0xb9b4eff6…c3ef
0x34b655…2a6f
4 touches
1 conflict
0xbaa2303d…243a
0x34b655…2a6f
4 touches
1 conflict
0xc15e7daf…9ba9
0x34b655…2a6f
4 touches
1 conflict
0xc1647db7…f853
0x34b655…2a6f
4 touches
1 conflict
0xe727ab72…768b
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x922c7ebd…6600
0xc8689a…ee79
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 0x7ee6007b44…92fd68
Audit this contract →
← previous block·next block →recent activity