pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,036,950
← previous block
next block →
recent activity
Analyzing
Block #72,036,950
8 transactions · 7 stateful · 2026-05-02 22:41:45 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,036,950
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f67e20
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x3f5c179b
#7
0x39435dac
#2
0x69f67e21
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
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x01b1c8a0…5b9e
0x065c9d…c394
2 touches
0 conflicts
0x1087df45…ff8c
0x065c9d…c394
2 touches
0 conflicts
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0x39badc9a…a7d0
0x065c9d…c394
2 touches
0 conflicts
0x92e544e2…ce1b
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity