← previous blocknext block →recent activity
Analyzing
Block #74,258,104
9 transactions · 8 stateful · 2026-05-13 05:34:39 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,258,104 · 9 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
1w02w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0x553ef5d1…a091
0x065c9d…c394
3 touches
1 conflict
0x5baad89f…7256
0x065c9d…c394
2 touches
0 conflicts
0x643b8fdb…e2be
0x065c9d…c394
2 touches
0 conflicts
0x66fe75d3…2b7a
0x065c9d…c394
2 touches
0 conflicts
0xb50ada9a…6cb7
0x065c9d…c394
2 touches
0 conflicts
0xbaa28b23…0402
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