← previous blocknext block →recent activity
Analyzing
Block #85,821,336
18 transactions · 14 stateful · 2026-07-05 19:13:22 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,821,336 · 18 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
2w05w16w110w011w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47622f44…e267
0x065c9d…c394
6 touches
3 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
6 touches
3 conflicts
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xdd70bea3…1ffe
0x3bd359…433a
2 touches
0 conflicts
0x676931a1…029d
0x754704…b603
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x47622f44ae…c3e267
Audit this contract →
← previous block·next block →recent activity