← previous blocknext block →recent activity
Analyzing
Block #74,429,776
10 transactions · 9 stateful · 2026-05-14 00:36:50 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,429,776 · 10 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
1w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd5a6b524…921f
0x065c9d…c394
3 touches
1 conflict
0x1e6046bf…1167
0x065c9d…c394
3 touches
1 conflict
0x1a930b5a…efce
0x065c9d…c394
2 touches
0 conflicts
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0x402d297a…12ac
0x065c9d…c394
2 touches
0 conflicts
0x5b463ea4…d68d
0x065c9d…c394
2 touches
0 conflicts
0x9597ae4a…2bf0
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity