← previous blocknext block →recent activity
Analyzing
Block #76,238,026
8 transactions · 7 stateful · 2026-05-22 09:55:50 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,238,026 · 8 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa2d71ec…90a8
0x065c9d…c394
4 touches
1 conflict
0x2f88a23f…9dc5
0x2a68ba…90c5
4 touches
1 conflict
0x5f6df0bf…c491
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f490f9…6563
0x065c9d…c394
3 touches
1 conflict
0xd6ae97fb…0667
0x065c9d…c394
3 touches
1 conflict
0x08f5605c…0530
0x065c9d…c394
3 touches
1 conflict
0x08f5605c…052f
0x065c9d…c394
3 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
1 conflict on slot 0xfa2d71ec4b…5890a8
Audit this contract →
← previous block·next block →recent activity