pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,167,896
← previous block
next block →
recent activity
Analyzing
Block #72,167,896
11 transactions · 10 stateful · 2026-05-03 13:13:31 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,167,896
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
revealWithCallback
#2
0x98717539
#3
approve
#4
0x3f5c179b
#5
forward
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
· blocks 1
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x65e795ca…0320
0x34b655…2a6f
4 touches
1 conflict
0xc7f28b7a…5777
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x4f2d42cd…569c
0x065c9d…c394
2 touches
0 conflicts
0x67822b7c…4860
0x065c9d…c394
2 touches
0 conflicts
0x7e5f2b3f…f3ed
0x065c9d…c394
2 touches
0 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity