← previous blocknext block →recent activity
Analyzing
Block #75,525,371
16 transactions · 9 stateful · 2026-05-19 02:46:23 UTC
Parallelism
88/100
Blocked
22%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,525,371 · 16 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
1w03w04w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe11ca6a3…8f7d
0x065c9d…c394
3 touches
1 conflict
0x56682e48…e158
0x065c9d…c394
3 touches
1 conflict
0xde8ee0d6…cc59
0xd32edf…ff58
3 touches
1 conflict
0x5f77d607…2c84
0x065c9d…c394
2 touches
0 conflicts
0x2f88a23f…9dc5
0x2a68ba…90c5
2 touches
0 conflicts
0x9bf064a6…4f04
0x2a68ba…90c5
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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