pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#72,498,585
← previous block
next block →
recent activity
Analyzing
Block #72,498,585
10 transactions · 8 stateful · 2026-05-05 02:03:50 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,498,585
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
handleOps
#4
0x1a945f9c
· blocks 1
#5
updateDataFeedsValuesPartial
#7
0x3f5c179b
#8
setData
#9
0x39435dac
#2
updatePrices
#6
0xd10227eb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0070
0x1efe02…37d6
2 touches
0 conflicts
0x1d5750ef…ebfd
0x1efe02…37d6
2 touches
0 conflicts
0x9b26ab1c…f6df
0x1efe02…37d6
2 touches
0 conflicts
0xbf3ce357…b959
0x1efe02…37d6
2 touches
0 conflicts
0x00bac013…a28c
0x91b81b…6d56
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:
0x7e9d3a8a…4f9fda
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity