← previous blocknext block →recent activity
Analyzing
Block #74,613,711
12 transactions · 9 stateful · 2026-05-14 21:08:42 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,613,711 · 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
1w02w15w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6b319071…a105
0xc8689a…ee79
4 touches
1 conflict
0x84b6ead2…c52d
0xd32edf…ff58
3 touches
1 conflict
0x5a72771d…c0e9
0x065c9d…c394
3 touches
1 conflict
0xce1a8e5b…5431
0x065c9d…c394
3 touches
1 conflict
0xe94e77ab…f017
0x5d823e…89c6
3 touches
1 conflict
0xf0f673fd…37a7
0x5d823e…89c6
3 touches
1 conflict
0x76561bd4…46ff
0x065c9d…c394
2 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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity