← previous blocknext block →recent activity
Analyzing
Block #74,905,505
7 transactions · 5 stateful · 2026-05-16 05:36:05 UTC
Parallelism
57/100
Blocked
40%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,905,505 · 7 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
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x317619f2…9f6b
0x065c9d…c394
4 touches
1 conflict
0x18b9292f…3d33
0x065c9d…c394
3 touches
1 conflict
0x16c86de6…aa38
0x065c9d…c394
2 touches
0 conflicts
0x22ee94ac…aee8
0x065c9d…c394
2 touches
0 conflicts
0xbeb80b73…5863
0x065c9d…c394
2 touches
0 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
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