← previous blocknext block →recent activity
Analyzing
Block #85,176,564
24 transactions · 22 stateful · 2026-07-02 19:38:22 UTC
Parallelism
75/100
Blocked
32%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,176,564 · 24 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
5w06w17w08w116w017w118w219w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x42c51fbb…4575
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x50ce3dd5…bfb4
0x34b655…2a6f
4 touches
1 conflict
0x5eb187dd…b1d6
0x34b655…2a6f
4 touches
1 conflict
0x5ffc25fa…b119
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity