← previous blocknext block →recent activity
Analyzing
Block #74,902,503
8 transactions · 8 stateful · 2026-05-16 05:16:05 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,902,503 · 8 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
1w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ce6b1b5…ca14
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x108aa04f…94a7
0x065c9d…c394
3 touches
1 conflict
0x5d275e30…fa78
0x065c9d…c394
3 touches
1 conflict
0x65c0c385…bf1a
0x065c9d…c394
2 touches
0 conflicts
0x9d2e313e…9db9
0x065c9d…c394
2 touches
0 conflicts
0xf3d7a307…4d63
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x0ce6b1b5ad…b3ca14
Audit this contract →
← previous block·next block →recent activity