pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,429,196
← previous block
next block →
recent activity
Analyzing
Block #76,429,196
12 transactions · 11 stateful · 2026-05-23 07:08:32 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,429,196
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1094dc9f
· blocks 1
#3
0x5339c59f
#4
0x5339c59f
#5
0x45761772
#6
0xc5a04723
#7
updateDataFeedsValuesPartial
#8
cancelLimitOrder
#9
0xe8891658
#10
transfer
#11
setData
#2
exactOutputSingle
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0x00000000…0003
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0xb1acfe51…c6b1
0x3bd359…433a
2 touches
0 conflicts
0xfe3bddd2…8b48
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0005
0x63e48b…53f2
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)
1 conflict on slot
0xf6cc7de8cb…7d0b4a
Audit this contract →
← previous block
·
next block →
recent activity