← previous blocknext block →recent activity
Analyzing
Block #74,803,670
20 transactions · 16 stateful · 2026-05-15 18:16:57 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,803,670 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w48w511w012w113w217w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d0b2509…074d
0x3bd359…433a
12 touches
15 conflicts
0xe6455d1f…1029
0x754704…b603
12 touches
15 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xa02838a3…bc54
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x31bd026b…43f0
0x065c9d…c394
3 touches
1 conflict
0xebd99a4d…e294
0x065c9d…c394
3 touches
1 conflict
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: Wrapped MON (WMON)
15 conflicts on slot 0x0d0b2509ae…4b074d
Audit this contract →
← previous block·next block →recent activity