pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,498,319
← previous block
next block →
recent activity
Analyzing
Block #72,498,319
10 transactions · 9 stateful · 2026-05-05 02:02:04 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,498,319
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
#2
updatePosition
#3
0x3f5c179b
#4
forward
#5
updateDataFeedsValuesPartial
#6
0x69f95014
#7
setData
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf17589f…048c
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x23951077…539b
0x34b655…2a6f
2 touches
0 conflicts
0x4f483049…3cc7
0x34b655…2a6f
2 touches
0 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
2 touches
0 conflicts
0xedb848fe…6534
0x34b655…2a6f
2 touches
0 conflicts
0x462c8be7…4f83
0x8d66a4…3095
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:
0x34b6552d…112a6f
1 conflict on slot
0xcf17589f89…ef048c
Audit this contract →
← previous block
·
next block →
recent activity