← previous blocknext block →recent activity
Analyzing
Block #76,194,184
14 transactions · 12 stateful · 2026-05-22 05:03:35 UTC
Parallelism
79/100
Blocked
17%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,194,184 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe2bac2b…2cec
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xa56a84d2…0dcd
0x000000…a032
2 touches
0 conflicts
0x2ddd4fb9…6778
0x065c9d…c394
2 touches
0 conflicts
0x6176d2fe…cc70
0x065c9d…c394
2 touches
0 conflicts
0x80b91de5…f0fb
0x065c9d…c394
2 touches
0 conflicts
0x9666a8d0…063d
0x065c9d…c394
2 touches
0 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: Market-MON/USDC
3 conflicts on slot 0xfe2bac2b2f…482cec
Audit this contract →
← previous block·next block →recent activity