← previous blocknext block →recent activity
Analyzing
Block #75,479,524
10 transactions · 7 stateful · 2026-05-18 21:32:00 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,479,524 · 10 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
1w03w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0aa885fa…a3d1
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x59335736…d27f
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x04b37132…a4f2
0x065c9d…c394
2 touches
0 conflicts
0x07d5dc87…f727
0x065c9d…c394
2 touches
0 conflicts
0xbbd94d46…c0c1
0x065c9d…c394
2 touches
0 conflicts
0xc6e79b2c…9d93
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: MarginAccount
1 conflict on slot 0x0aa885fa2f…33a3d1
Audit this contract →
← previous block·next block →recent activity