← previous blocknext block →recent activity
Analyzing
Block #76,559,482
22 transactions · 17 stateful · 2026-05-23 21:36:10 UTC
Parallelism
82/100
Blocked
47%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,559,482 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w07w09w110w213w114w317w119w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
6 touches
3 conflicts
0xdfa159d0…1576
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0aa885fa…a3d1
0x2a68ba…90c5
6 touches
3 conflicts
0xb7b446d2…2006
0x34b655…2a6f
6 touches
3 conflicts
0x68acb530…ad69
0xd32edf…ff58
5 touches
3 conflicts
0x1fff6dcb…b3f4
0xc8689a…ee79
4 touches
1 conflict
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity