← previous blocknext block →recent activity
Analyzing
Block #76,284,278
14 transactions · 12 stateful · 2026-05-22 15:03:28 UTC
Parallelism
79/100
Blocked
25%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,284,278 · 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
1w03w04w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x5e6b612c…078e
0x065c9d…c394
2 touches
0 conflicts
0x71baee52…e865
0x065c9d…c394
2 touches
0 conflicts
0x71c0fe0a…e00a
0x065c9d…c394
2 touches
0 conflicts
0x961f2753…5ad7
0x065c9d…c394
2 touches
0 conflicts
0xc72f5619…a9a9
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity