← previous blocknext block →recent activity
Analyzing
Block #86,635,141
30 transactions · 23 stateful · 2026-07-09 13:48:29 UTC
Parallelism
87/100
Blocked
52%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,635,141 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w16w27w08w19w010w111w217w019w021w122w123w227w128w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x56c67d02…56e7
0xd32edf…ff58
5 touches
3 conflicts
0x4a4c3d20…bd65
0x3bd359…433a
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0x6f845aff…9fc9
0x3bd359…433a
4 touches
1 conflict
0xc6101b5d…4361
0x3bd359…433a
4 touches
1 conflict
0x062b2598…4e28
0x43cf54…7777
4 touches
1 conflict
0x0db0aaac…e94d
0x43cf54…7777
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity