← previous blocknext block →recent activity
Analyzing
Block #76,090,995
17 transactions · 12 stateful · 2026-05-21 17:36:23 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,090,995 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w36w410w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xfdd32467…8921
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x2d3f14d0…e0cd
0x065c9d…c394
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: MarginAccount
3 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity