← previous blocknext block →recent activity
Analyzing
Block #76,226,495
12 transactions · 10 stateful · 2026-05-22 08:38:57 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,226,495 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x3a6e7600…e1f1
0xa6afd3…d132
4 touches
1 conflict
0x1e0da364…115f
0x065c9d…c394
2 touches
0 conflicts
0x31429844…f339
0x065c9d…c394
2 touches
0 conflicts
0x56d13504…0989
0x065c9d…c394
2 touches
0 conflicts
0x61f21a7f…cd02
0x065c9d…c394
2 touches
0 conflicts
0xacc7b7fc…cdf0
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity