← previous blocknext block →recent activity
Analyzing
Block #85,512,294
25 transactions · 19 stateful · 2026-07-04 08:54:11 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,512,294 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w09w010w111w012w113w015w116w218w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54b193ad…c830
0x34b655…2a6f
6 touches
3 conflicts
0xca0f0668…caf3
0xa6afd3…d132
6 touches
3 conflicts
0x518f2037…e422
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x4be73d60…d0b5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x54b193ad55…f5c830
Audit this contract →
← previous block·next block →recent activity