← previous blocknext block →recent activity
Analyzing
Block #74,266,883
10 transactions · 10 stateful · 2026-05-13 06:33:02 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,266,883 · 10 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
1w05w16w2
- 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
0xf823e97f…2ee6
0x065c9d…c394
4 touches
1 conflict
0x0d57388f…e430
0x065c9d…c394
2 touches
0 conflicts
0x12625085…8905
0x065c9d…c394
2 touches
0 conflicts
0x3bc2e97a…4077
0x065c9d…c394
2 touches
0 conflicts
0x58d60d99…e337
0x065c9d…c394
2 touches
0 conflicts
0x637904e4…339b
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