← previous blocknext block →recent activity
Analyzing
Block #74,409,843
17 transactions · 9 stateful · 2026-05-13 22:24:14 UTC
Parallelism
88/100
Blocked
11%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,409,843 · 17 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
1w02w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x83f71049…1b3f
0x065c9d…c394
3 touches
1 conflict
0x005a6eab…86e6
0x065c9d…c394
2 touches
0 conflicts
0x26f2ebac…3ffa
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0xe58c3a52…014b
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
1 conflict on slot 0x47b807a243…c53307
Audit this contract →
← previous block·next block →recent activity