← previous blocknext block →recent activity
Analyzing
Block #74,406,341
16 transactions · 14 stateful · 2026-05-13 22:00:55 UTC
Parallelism
81/100
Blocked
14%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,406,341 · 16 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
1w02w111w013w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47b807a2…3307
0x065c9d…c394
6 touches
3 conflicts
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x8f7d9d32…fa70
0x065c9d…c394
3 touches
1 conflict
0xcec551d3…ba09
0xd32edf…ff58
3 touches
1 conflict
0xce8bbe33…b72e
0x3bd359…433a
2 touches
0 conflicts
0x2e2214a9…fe0d
0x5d823e…89c6
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 0x47b807a243…c53307
Audit this contract →
← previous block·next block →recent activity