← previous blocknext block →recent activity
Analyzing
Block #86,987,515
24 transactions · 18 stateful · 2026-07-11 05:04:10 UTC
Parallelism
71/100
Blocked
39%
Avg conflicts / tx
0.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,987,515 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w09w110w211w315w417w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9bc1dfc…6bfb
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x91d5e8db…4c65
0x34b655…2a6f
4 touches
1 conflict
0x9f40a209…1193
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 0xb9bc1dfc6a…676bfb
Audit this contract →
← previous block·next block →recent activity