pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,223,250
← previous block
next block →
recent activity
Analyzing
Block #76,223,250
10 transactions · 7 stateful · 2026-05-22 08:17:10 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,223,250
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
executeBatch
#7
setData
#8
0x0c7abd22
· blocks 1
#9
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb45d9d6…cb87
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0xf85c75bc…00b5
0xa6afd3…d132
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x214bdbf2…c926
0xd32edf…ff58
3 touches
1 conflict
0xdb9d8189…e926
0xa6afd3…d132
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:
ShMonad (shMON)
1 conflict on slot
0xcb45d9d62a…b1cb87
Audit this contract →
← previous block
·
next block →
recent activity