← previous blocknext block →recent activity
Analyzing
Block #75,792,431
12 transactions · 8 stateful · 2026-05-20 08:25:50 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,792,431 · 12 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
1w02w15w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x2f88a23f…9dc5
0x2a68ba…90c5
4 touches
1 conflict
0x31a326b6…2b32
0x065c9d…c394
3 touches
1 conflict
0xc642e66c…d4d7
0x065c9d…c394
3 touches
1 conflict
0x31a326b6…2b33
0x065c9d…c394
3 touches
1 conflict
0xe9439ef7…a67b
0x065c9d…c394
2 touches
0 conflicts
0x09beabbc…065c
0x188d58…ea8e
2 touches
0 conflicts
0x09beabbc…065e
0x188d58…ea8e
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity