← previous blocknext block →recent activity
Analyzing
Block #74,666,054
7 transactions · 7 stateful · 2026-05-15 02:57:58 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,666,054 · 7 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x65076518…320d
0x065c9d…c394
4 touches
1 conflict
0xc358dbfb…4db2
0x065c9d…c394
3 touches
1 conflict
0x3ae52531…1c8c
0x065c9d…c394
2 touches
0 conflicts
0x58177a9b…586f
0x065c9d…c394
2 touches
0 conflicts
0xee588687…55b0
0x065c9d…c394
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity