← previous blocknext block →recent activity
Analyzing
Block #74,319,351
15 transactions · 14 stateful · 2026-05-13 12:22:07 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,319,351 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w18w19w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24968e6d…0132
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x44ad89ba…cf83
0xde22b2…7777
4 touches
1 conflict
0x00000000…0001
0x776059…1d8d
4 touches
1 conflict
0x00000000…0000
0x776059…1d8d
4 touches
1 conflict
0xbf25e763…684f
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x9b1a47c3…69f8
0xde22b2…7777
4 touches
1 conflict
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 0x24968e6db4…f00132
Audit this contract →
← previous block·next block →recent activity