pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,457,916
← previous block
next block →
recent activity
Analyzing
Block #72,457,916
9 transactions · 8 stateful · 2026-05-04 21:33:09 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,457,916
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f9110c
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
setData
#5
0x3f5c179b
#6
0x6df9e92b
· blocks 1
#8
0x69f9110c
#7
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x579d00…83f8
4 touches
1 conflict
0x00000000…0002
0x579d00…83f8
4 touches
1 conflict
0x399cd013…b14f
0x23ae8c…7777
4 touches
1 conflict
0x44ad89ba…cf83
0x23ae8c…7777
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0xb4b3c404…f0aa
0x3bd359…433a
4 touches
1 conflict
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:
0x579d005c…ab83f8
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity