← previous blocknext block →recent activity
Analyzing
Block #86,152,475
14 transactions · 12 stateful · 2026-07-07 08:02:22 UTC
Parallelism
57/100
Blocked
58%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,152,475 · 14 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
1w02w05w06w17w19w110w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x4546ebad…b908
0x34b655…2a6f
6 touches
3 conflicts
0x13a5a8fa…2b18
0x34b655…2a6f
6 touches
3 conflicts
0x4164f3d1…3d0e
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x05edf2cf…ac3c
0x34b655…2a6f
6 touches
3 conflicts
0x4eb98096…65c2
0x34b655…2a6f
6 touches
3 conflicts
0x594c318b…c3d2
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity