← previous blocknext block →recent activity
Analyzing
Block #76,237,762
21 transactions · 18 stateful · 2026-05-22 09:54:04 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #76,237,762 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w26w37w48w09w111w112w013w116w217w519w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe2bac2b…2cec
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2b0294d…3968
0xd32edf…ff58
7 touches
6 conflicts
0x0aa885fa…a3d1
0x2a68ba…90c5
6 touches
3 conflicts
0xf3d7a307…4d63
0x065c9d…c394
6 touches
3 conflicts
0xa605468c…1bfc
0x1d1325…2305
4 touches
1 conflict
0xc8525006…2b45
0x1d1325…2305
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
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
10 conflicts on slot 0xfe2bac2b2f…482cec
Audit this contract →
← previous block·next block →recent activity