pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,283,364
← previous block
next block →
recent activity
Analyzing
Block #72,283,364
12 transactions · 11 stateful · 2026-05-04 02:09:25 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,283,364
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0x0f052239
#3
0x98c01e2a
#4
0x15ea9545
· blocks 1
#5
0x98717539
#6
updateDataFeedsValuesPartial
#7
0x0c7abd22
· blocks 1
#10
setData
#11
0x39435dac
#8
0x0c7abd22
#9
0x366fe5db
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w0
8
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1728ed63…499c
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0xdfc0447b…6221
0xd32edf…ff58
3 touches
1 conflict
0x76498d82…2995
0x000000…012a
2 touches
0 conflicts
0x69b34e04…d397
0x065c9d…c394
2 touches
0 conflicts
0x74e71984…ae90
0x2a68ba…90c5
2 touches
0 conflicts
0x74fe76c9…225f
0x3bd359…433a
2 touches
0 conflicts
0xcce2fd99…a8eb
0x3bd359…433a
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:
0xea1b8e4a…8fc5ec
1 conflict on slot
0x1728ed6317…a9499c
Audit this contract →
← previous block
·
next block →
recent activity