pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,286,072
← previous block
next block →
recent activity
Analyzing
Block #74,286,072
9 transactions · 9 stateful · 2026-05-13 08:40:37 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,286,072
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
collect
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x6a04397d
· blocks 1
#5
setData
#7
0x39435dac
· blocks 1
#6
0x6a04397d
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef17b8cd…9511
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x24cfe713…0f91
0x25d593…7777
2 touches
0 conflicts
0x8e07e07d…65ff
0x30611e…d8d9
2 touches
0 conflicts
0x8e07e07d…6600
0x30611e…d8d9
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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:
Perpl
1 conflict on slot
0xef17b8cd5c…709511
Audit this contract →
← previous block
·
next block →
recent activity