← previous blocknext block →recent activity
Analyzing
Block #74,396,131
15 transactions · 11 stateful · 2026-05-13 20:52:54 UTC
Parallelism
80/100
Blocked
18%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,396,131 · 15 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
2w03w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0xfd6983f8…188c
0x065c9d…c394
3 touches
1 conflict
0x369894c5…6c03
0x065c9d…c394
3 touches
1 conflict
0xe0cfba04…83b5
0x065c9d…c394
2 touches
0 conflicts
0xe40b3e0d…38cf
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity