← previous blocknext block →recent activity
Analyzing
Block #74,787,306
11 transactions · 11 stateful · 2026-05-15 16:27:44 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,787,306 · 11 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
1w02w15w28w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x372e8e9e…3939
0x065c9d…c394
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x56f1d983…fd06
0x065c9d…c394
3 touches
1 conflict
0xba0163a6…e57c
0x065c9d…c394
3 touches
1 conflict
0x6c3d188e…8fce
0x065c9d…c394
2 touches
0 conflicts
0xa9838c09…7ecd
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