← previous blocknext block →recent activity
Analyzing
Block #85,814,221
14 transactions · 13 stateful · 2026-07-05 18:26:03 UTC
Parallelism
86/100
Blocked
15%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,814,221 · 14 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
1w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x60dc44c7…999c
0x065c9d…c394
4 touches
1 conflict
0x585771af…0c2e
0x065c9d…c394
3 touches
1 conflict
0xbfcaf88b…5810
0x065c9d…c394
3 touches
1 conflict
0xd9b414d7…e0e1
0x065c9d…c394
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x06e40499…165e
0x69df8a…6292
2 touches
0 conflicts
0xa605468c…1bfc
0x69df8a…6292
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity