pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,213,443
← previous block
next block →
recent activity
Analyzing
Block #72,213,443
8 transactions · 8 stateful · 2026-05-03 18:19:34 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,213,443
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f7922d
#2
updatePrices
· blocks 1
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x3f5c179b
#7
0x6df9e92b
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0262b369…b3b7
0x065c9d…c394
2 touches
0 conflicts
0x66d18879…a6d4
0x065c9d…c394
2 touches
0 conflicts
0x9a754c2e…15f5
0x065c9d…c394
2 touches
0 conflicts
0xa7477eac…c855
0x065c9d…c394
2 touches
0 conflicts
0xb97ab433…80b0
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:
0x7e9d3a8a…4f9fda
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity