← previous blocknext block →recent activity
Analyzing
Block #76,387,377
22 transactions · 19 stateful · 2026-05-23 02:30:32 UTC
Parallelism
50/100
Blocked
58%
Avg conflicts / tx
1.95
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #76,387,377 · 22 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w69w710w811w913w717w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3c8642a…7da5
0x2a68ba…90c5
14 touches
21 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x353ef497…1399
0x065c9d…c394
11 touches
15 conflicts
0x55860cba…06ce
0xd32edf…ff58
11 touches
15 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 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
21 conflicts on slot 0xc3c8642ae9…317da5
Audit this contract →
← previous block·next block →recent activity