← previous blocknext block →recent activity
Analyzing
Block #74,396,016
11 transactions · 7 stateful · 2026-05-13 20:52:08 UTC
Parallelism
82/100
Blocked
14%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,396,016 · 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
2w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8041dd1…50d4
0x065c9d…c394
4 touches
1 conflict
0x11d60426…9be6
0x065c9d…c394
3 touches
1 conflict
0xa1febcc3…1437
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x23bbc51d…668c
0x065c9d…c394
2 touches
0 conflicts
0x72fbfb06…ae5a
0x065c9d…c394
2 touches
0 conflicts
0xe8805f31…806c
0x065c9d…c394
2 touches
0 conflicts
0xedd9b2e7…3e8f
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 0xf8041dd18d…c250d4
Audit this contract →
← previous block·next block →recent activity