← previous blocknext block →recent activity
Analyzing
Block #85,219,715
15 transactions · 14 stateful · 2026-07-03 00:25:45 UTC
Parallelism
60/100
Blocked
43%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,219,715 · 15 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
3w04w15w06w27w110w311w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd63e616b…a07d
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0110331c…b891
0x34b655…2a6f
4 touches
1 conflict
0x09ce76d1…b412
0x34b655…2a6f
4 touches
1 conflict
0x0db8e93a…7dd1
0x34b655…2a6f
4 touches
1 conflict
0x1c1a8b8d…c225
0x34b655…2a6f
4 touches
1 conflict
0x2267f8c4…a571
0x34b655…2a6f
4 touches
1 conflict
0x2697123c…8526
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 0xd63e616b67…7fa07d
Audit this contract →
← previous block·next block →recent activity