← previous blocknext block →recent activity
Analyzing
Block #85,104,004
10 transactions · 9 stateful · 2026-07-02 11:34:10 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,104,004 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59ed335a…d2f3
0x34b655…2a6f
4 touches
1 conflict
0xd680d6d2…e522
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x79b3209b…f766
0x34b655…2a6f
4 touches
1 conflict
0x442f3445…286c
0x34b655…2a6f
2 touches
0 conflicts
0x4a30aa35…d21a
0x34b655…2a6f
2 touches
0 conflicts
0x6b206d7f…2f23
0x34b655…2a6f
2 touches
0 conflicts
0x76866f31…c9d6
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 0x59ed335a81…67d2f3
Audit this contract →
← previous block·next block →recent activity