← previous blocknext block →recent activity
Analyzing
Block #74,948,971
11 transactions · 9 stateful · 2026-05-16 10:26:29 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,948,971 · 11 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11e92674…f15c
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5c35f6c1…de13
0x065c9d…c394
3 touches
1 conflict
0x06a3e0ac…9874
0x065c9d…c394
2 touches
0 conflicts
0x65ffeff6…c3e2
0x065c9d…c394
2 touches
0 conflicts
0x9e3e33a8…fcb1
0x065c9d…c394
2 touches
0 conflicts
0xaf5966b6…55da
0x065c9d…c394
2 touches
0 conflicts
0xd812e123…6cb8
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 0x11e92674f1…38f15c
Audit this contract →
← previous block·next block →recent activity