pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,171,662
← previous block
next block →
recent activity
Analyzing
Block #72,171,662
10 transactions · 8 stateful · 2026-05-03 13:38:47 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,171,662
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xfa88789d
· blocks 1
#3
0x69f7505f
#4
0x3f5c179b
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x69f7505e
#9
setData
#2
0xfa88789d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x67d1be…196f
4 touches
1 conflict
0x2b936aa5…05e5
0x141b1d…9583
4 touches
1 conflict
0x00000000…0003
0x2ae0cf…3d4e
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x9e9407e5…9124
0x065c9d…c394
2 touches
0 conflicts
0xc13f2587…a1d6
0x065c9d…c394
2 touches
0 conflicts
0xccb780a3…5011
0x065c9d…c394
2 touches
0 conflicts
0xd09312c2…5ae1
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:
0x67d1be51…42196f
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity