← previous blocknext block →recent activity
Analyzing
Block #74,924,537
8 transactions · 6 stateful · 2026-05-16 07:43:06 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,924,537 · 8 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xaa351ead…a686
0x065c9d…c394
4 touches
1 conflict
0x048dfc7b…8c71
0x065c9d…c394
4 touches
1 conflict
0x0b70d01f…282d
0x065c9d…c394
3 touches
1 conflict
0xb453af9f…d5a2
0x065c9d…c394
3 touches
1 conflict
0x4a27d882…8210
0x065c9d…c394
3 touches
1 conflict
0x977ddc55…30e0
0x065c9d…c394
3 touches
1 conflict
0xa7fa5dbb…b45c
0x065c9d…c394
3 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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity