pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#72,167,343
← previous block
next block →
recent activity
Analyzing
Block #72,167,343
12 transactions · 12 stateful · 2026-05-03 13:09:48 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,167,343
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
0x69f74994
#3
exactOutputSingle
#4
exactOutputSingle
#5
execute
#6
updatePrices
#7
0x98717539
· blocks 1
#9
updateDataFeedsValuesPartial
#10
0x3f5c179b
#11
setData
#8
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x041ee703…b4c1
0x34b655…2a6f
4 touches
1 conflict
0x0d2947c3…98d6
0x34b655…2a6f
4 touches
1 conflict
0x17e2d2a0…359e
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x3254d19b…f714
0x34b655…2a6f
4 touches
1 conflict
0x3347cbe5…846c
0x34b655…2a6f
4 touches
1 conflict
0x414e9446…4b59
0x34b655…2a6f
4 touches
1 conflict
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
0x041ee703a0…a8b4c1
Audit this contract →
← previous block
·
next block →
recent activity