← previous blocknext block →recent activity
Analyzing
Block #85,508,331
16 transactions · 13 stateful · 2026-07-04 08:27:51 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,508,331 · 16 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
7w010w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0b3a72d1…718e
0x065c9d…c394
2 touches
0 conflicts
0x1532f1c3…66a4
0x065c9d…c394
2 touches
0 conflicts
0x4612c45d…3b6b
0x065c9d…c394
2 touches
0 conflicts
0x4c9e0fe5…8da0
0x065c9d…c394
2 touches
0 conflicts
0x5f918e51…d9b2
0x065c9d…c394
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 0x0ab54c30a6…82b88e
Audit this contract →
← previous block·next block →recent activity