← previous blocknext block →recent activity
Analyzing
Block #76,111,639
21 transactions · 17 stateful · 2026-05-21 19:53:53 UTC
Parallelism
90/100
Blocked
24%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,111,639 · 21 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
1w02w03w14w18w010w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc48fab0…6bf5
0x065c9d…c394
4 touches
1 conflict
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0xf9b8ae99…32b3
0x34b655…2a6f
4 touches
1 conflict
0xf9b8ae99…32b4
0x34b655…2a6f
4 touches
1 conflict
0x15dfc675…c5e2
0xa6afd3…d132
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0x557bc513…46d9
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
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: Market-MON/USDC
1 conflict on slot 0xcc48fab001…576bf5
Audit this contract →
← previous block·next block →recent activity