pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,166,945
← previous block
next block →
recent activity
Analyzing
Block #76,166,945
9 transactions · 9 stateful · 2026-05-22 02:02:17 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,166,945
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5bf9264c
#2
updateDataFeedsValuesPartial
#3
0x6df9e92b
· blocks 2
#6
setData
#7
redeemDelegations
#8
modifyLiquidities
#4
0x6df9e92b
· blocks 1
#5
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0xe3ee7f9e…f356
0x3bd359…433a
4 touches
1 conflict
0x24cfe713…0f91
0x25d593…7777
4 touches
1 conflict
0x44ad89ba…cf83
0x25d593…7777
4 touches
1 conflict
0x00000000…0000
0x30611e…d8d9
4 touches
1 conflict
0x00000000…0002
0x30611e…d8d9
4 touches
1 conflict
0x99a3a7c1…1e2b
0x0cc9b2…7777
2 touches
0 conflicts
0xf0c05263…9a0d
0x0cc9b2…7777
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:
Wrapped MON (WMON)
3 conflicts on slot
0xa472d565a0…ae9fe4
Audit this contract →
← previous block
·
next block →
recent activity