← previous blocknext block →recent activity
Analyzing
Block #85,786,997
13 transactions · 11 stateful · 2026-07-05 15:24:39 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,786,997 · 13 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
1w04w06w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca2926e0…61b5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0xe7d03430…157d
0x065c9d…c394
4 touches
1 conflict
0xf8f6033b…09d7
0x065c9d…c394
4 touches
1 conflict
0x49908556…f6c5
0x065c9d…c394
3 touches
1 conflict
0xca26a37c…5759
0x065c9d…c394
3 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
1 conflict on slot 0xca2926e0af…1961b5
Audit this contract →
← previous block·next block →recent activity