← previous blocknext block →recent activity
Analyzing
Block #85,516,567
7 transactions · 5 stateful · 2026-07-04 09:22:41 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,516,567 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1fdeff02…6d28
0x34b655…2a6f
4 touches
1 conflict
0x95b76c4f…c6f6
0x34b655…2a6f
4 touches
1 conflict
0x2832afc3…93c4
0x34b655…2a6f
2 touches
0 conflicts
0x6b2a6570…0e70
0x34b655…2a6f
2 touches
0 conflicts
0x6f7a92ed…5651
0x34b655…2a6f
2 touches
0 conflicts
0x7431a49d…c3d6
0x34b655…2a6f
2 touches
0 conflicts
0x8e5cc690…b06b
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
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity