← previous blocknext block →recent activity
Analyzing
Block #74,313,346
12 transactions · 9 stateful · 2026-05-13 11:42:09 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,313,346 · 12 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
1w05w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c5d7ca6…bc5d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xbbee74c2…567a
0x065c9d…c394
4 touches
1 conflict
0xf219e53d…1a9a
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xdc789cf0…69a7
0x065c9d…c394
3 touches
1 conflict
0x5ab1cef4…67ef
0x065c9d…c394
3 touches
1 conflict
0x83386370…df56
0x065c9d…c394
3 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
1 conflict on slot 0x2c5d7ca649…bdbc5d
Audit this contract →
← previous block·next block →recent activity