← previous blocknext block →recent activity
Analyzing
Block #86,964,500
17 transactions · 13 stateful · 2026-07-11 02:30:27 UTC
Parallelism
82/100
Blocked
23%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,964,500 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w19w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35d95fb0…db9e
0x34b655…2a6f
4 touches
1 conflict
0x60c7217a…8c94
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x35d95fb0…db9f
0x34b655…2a6f
4 touches
1 conflict
0xb652c396…b8fa
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf29e5320…ce2d
0x34b655…2a6f
4 touches
1 conflict
0xab81df09…b0db
0x34b655…2a6f
3 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 0x35d95fb08d…29db9e
Audit this contract →
← previous block·next block →recent activity