← previous blocknext block →recent activity
Analyzing
Block #85,747,256
12 transactions · 8 stateful · 2026-07-05 11:00:05 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,747,256 · 12 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
1w02w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd5cdb7b…d0e9
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0a399635…96f2
0x065c9d…c394
3 touches
1 conflict
0x192b9fe0…fe75
0x065c9d…c394
3 touches
1 conflict
0x2e73d8a8…0932
0x065c9d…c394
2 touches
0 conflicts
0x4533cc44…b192
0x065c9d…c394
2 touches
0 conflicts
0x97aef3f6…bbbf
0x065c9d…c394
2 touches
0 conflicts
0xde9fc5f8…104d
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0xfd5cdb7b98…23d0e9
Audit this contract →
← previous block·next block →recent activity