← previous blocknext block →recent activity
Analyzing
Block #85,282,296
11 transactions · 9 stateful · 2026-07-03 07:22:37 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,282,296 · 11 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
2w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc3f7ee8…7924
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x89c7ec3b…85ba
0x34b655…2a6f
4 touches
1 conflict
0x031112b4…3314
0x34b655…2a6f
2 touches
0 conflicts
0x1012ce23…9510
0x34b655…2a6f
2 touches
0 conflicts
0x11eaf6fb…cfe4
0x34b655…2a6f
2 touches
0 conflicts
0x12573732…e891
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
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 0xcc3f7ee8e4…307924
Audit this contract →
← previous block·next block →recent activity