← previous blocknext block →recent activity
Analyzing
Block #74,023,695
7 transactions · 6 stateful · 2026-05-12 03:35:31 UTC
Parallelism
43/100
Blocked
50%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,023,695 · 7 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
2w03w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0x018e27eb…7367
0x065c9d…c394
2 touches
0 conflicts
0x30e87049…4a0e
0x065c9d…c394
2 touches
0 conflicts
0x8aa773f7…e42d
0x065c9d…c394
2 touches
0 conflicts
0x9486b8b4…8340
0x065c9d…c394
2 touches
0 conflicts
0x9ff07992…6daa
0x065c9d…c394
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity