← previous blocknext block →recent activity
Analyzing
Block #74,518,080
12 transactions · 8 stateful · 2026-05-14 10:25:55 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,518,080 · 12 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1628c457…21da
0x065c9d…c394
4 touches
1 conflict
0x3bb3b667…224e
0x065c9d…c394
3 touches
1 conflict
0xc33178b1…9d3b
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1be681c7…a3cb
0x065c9d…c394
2 touches
0 conflicts
0x250fa399…7d69
0x065c9d…c394
2 touches
0 conflicts
0x2602dc73…8c7c
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
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 0x1628c45792…7721da
Audit this contract →
← previous block·next block →recent activity