← previous blocknext block →recent activity
Analyzing
Block #85,958,392
15 transactions · 14 stateful · 2026-07-06 10:26:39 UTC
Parallelism
73/100
Blocked
21%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,958,392 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w010w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xd35bb5ac…3586
0x065c9d…c394
6 touches
3 conflicts
0x0169c824…3810
0x065c9d…c394
4 touches
1 conflict
0x266d3a68…f8e4
0x065c9d…c394
3 touches
1 conflict
0x823c6413…3c85
0x065c9d…c394
3 touches
1 conflict
0xf597574d…94c8
0x065c9d…c394
3 touches
1 conflict
0xa4f80979…4d71
0x065c9d…c394
2 touches
0 conflicts
0xc16d3807…c645
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity