pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,288,382
← previous block
next block →
recent activity
Analyzing
Block #72,288,382
16 transactions · 11 stateful · 2026-05-04 02:43:09 UTC
Parallelism
81
/100
Blocked
18
%
Avg conflicts / tx
0.19
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,288,382
· 16 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
transfer
#3
0x69f80835
· blocks 2
#6
0x69f80835
#7
0x69f80835
#8
0xa96df62f
#9
0x69f80835
#10
updateDataFeedsValuesPartial
#11
0x3f5c179b
#12
forward
#13
0x69f80835
#14
setData
#15
0x39435dac
#4
0x69f80835
· blocks 1
#5
0x69f80835
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
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
0x1b6862…e19c
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
3 conflicts on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity