← previous blocknext block →recent activity
Analyzing
Block #86,365,229
13 transactions · 13 stateful · 2026-07-08 07:42:52 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,365,229 · 13 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
1w02w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5ec7eabe…e1f3
0x065c9d…c394
3 touches
1 conflict
0x451d04b9…4e3f
0x065c9d…c394
3 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
2 touches
0 conflicts
0x207741e7…da11
0x065c9d…c394
2 touches
0 conflicts
0x21dba876…61f5
0x065c9d…c394
2 touches
0 conflicts
0x553f10c4…9c64
0x065c9d…c394
2 touches
0 conflicts
0x711b2aef…8d38
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity