← previous blocknext block →recent activity
Analyzing
Block #74,771,350
10 transactions · 9 stateful · 2026-05-15 14:41:07 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,771,350 · 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
0xb7da88fc…fb38
0x065c9d…c394
3 touches
1 conflict
0x05adc348…4184
0x065c9d…c394
3 touches
1 conflict
0x2d48283a…6b33
0x065c9d…c394
2 touches
0 conflicts
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0x615a37fe…4913
0x065c9d…c394
2 touches
0 conflicts
0x7c4b7c4a…6ed9
0x065c9d…c394
2 touches
0 conflicts
0xd5a488e8…714b
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