← previous blocknext block →recent activity
Analyzing
Block #74,341,735
7 transactions · 6 stateful · 2026-05-13 14:50:56 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,341,735 · 7 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
1w03w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd3ca1f0a…b10c
0x065c9d…c394
4 touches
1 conflict
0x2f8d4891…ab33
0x065c9d…c394
4 touches
1 conflict
0x41d8579b…25de
0x065c9d…c394
3 touches
1 conflict
0x5d5740ff…14d1
0x065c9d…c394
2 touches
0 conflicts
0x847c252c…294f
0x065c9d…c394
2 touches
0 conflicts
0xd29b6af0…75ee
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity