← previous blocknext block →recent activity
Analyzing
Block #86,625,585
34 transactions · 20 stateful · 2026-07-09 12:44:35 UTC
Parallelism
91/100
Blocked
30%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,625,585 · 34 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
1w05w110w014w015w118w125w226w030w131w032w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x90a9bfb4…55d4
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0002
0x116e7d…d8f1
4 touches
1 conflict
0x00000000…0003
0x116e7d…d8f1
4 touches
1 conflict
0x895303cc…6f57
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0x116e7d…d8f1
4 touches
1 conflict
0x272e5bd6…252d
0x34b655…2a6f
4 touches
1 conflict
0x2bf5914f…c75d
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity