← previous blocknext block →recent activity
Analyzing
Block #85,811,147
19 transactions · 13 stateful · 2026-07-05 18:05:35 UTC
Parallelism
84/100
Blocked
23%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,811,147 · 19 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
1w05w06w112w014w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x0110331c…b891
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x38a31730…6687
0x065c9d…c394
4 touches
1 conflict
0x5c3cafb4…b7c9
0x065c9d…c394
3 touches
1 conflict
0x2c6af9b7…4ea4
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity