← previous blocknext block →recent activity
Analyzing
Block #85,282,151
15 transactions · 13 stateful · 2026-07-03 07:21:39 UTC
Parallelism
53/100
Blocked
46%
Avg conflicts / tx
1.27
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,282,151 · 15 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
1w05w16w27w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2406ccf7…c1cb
0x34b655…2a6f
12 touches
15 conflicts
0x5609b23e…c0a5
0x34b655…2a6f
10 touches
10 conflicts
0x5eb187dd…b1d6
0x34b655…2a6f
6 touches
3 conflicts
0xac61c3cf…cf4f
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x87804fa8…ff4b
0x34b655…2a6f
4 touches
1 conflict
0x9796e441…188b
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
15 conflicts on slot 0x2406ccf7d1…d8c1cb
Audit this contract →
← previous block·next block →recent activity