← previous blocknext block →recent activity
Analyzing
Block #76,237,048
14 transactions · 12 stateful · 2026-05-22 09:49:18 UTC
Parallelism
64/100
Blocked
42%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,237,048 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w49w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x067ca5fc…746f
0x065c9d…c394
2 touches
0 conflicts
0x6aed98d6…f068
0x065c9d…c394
2 touches
0 conflicts
0x73393e1e…8f38
0x065c9d…c394
2 touches
0 conflicts
0x75871297…f5f5
0x065c9d…c394
2 touches
0 conflicts
0x9e6bb027…0da2
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: 0xab35264b…1cfa38
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity