← previous blocknext block →recent activity
Analyzing
Block #86,320,203
22 transactions · 20 stateful · 2026-07-08 02:42:22 UTC
Parallelism
73/100
Blocked
35%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,320,203 · 22 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
2w03w110w214w116w217w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xf324b405…ca30
0x34b655…2a6f
6 touches
3 conflicts
0x298bd22e…b634
0x34b655…2a6f
6 touches
3 conflicts
0x3e505a15…70f8
0x34b655…2a6f
6 touches
3 conflicts
0x6f1a10f8…5a04
0x34b655…2a6f
6 touches
3 conflicts
0x727fbce7…0c80
0x34b655…2a6f
6 touches
3 conflicts
0x97785d36…2ac5
0x34b655…2a6f
6 touches
3 conflicts
0xa1571d54…ae41
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity