← previous blocknext block →recent activity
Analyzing
Block #74,428,435
10 transactions · 8 stateful · 2026-05-14 00:27:53 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,428,435 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbee74c2…567a
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa08f5228…4d9f
0x065c9d…c394
3 touches
1 conflict
0xa08f5228…4d9e
0x065c9d…c394
3 touches
1 conflict
0x840e7caa…2db0
0x065c9d…c394
3 touches
1 conflict
0xddb5ddde…f06f
0x065c9d…c394
3 touches
1 conflict
0x18253118…ebce
0xff20ac…1c43
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
3 conflicts on slot 0xbbee74c2e7…6e567a
Audit this contract →
← previous block·next block →recent activity