pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,037,476
← previous block
next block →
recent activity
Analyzing
Block #71,037,476
15 transactions · 14 stateful · 2026-04-28 07:42:19 UTC
Parallelism
80
/100
Blocked
29
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,037,476
· 15 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute_route
· blocks 3
#4
0x69f06553
#5
execute
#8
exec
#9
0x98717539
#10
0x98717539
#11
updateDataFeedsValuesPartial
#12
0x0c7abd22
#13
forward
#14
setData
#2
execute_route
· blocks 1
#3
exactInput
· blocks 1
#6
exactInputSingle
#7
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
6
w2
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a555477…19a8
0x754704…b603
6 touches
3 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0002
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0004
0x63e48b…53f2
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6e
0x188d58…ea8e
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:
0x754704bc…afb603
3 conflicts on slot
0x9a55547719…9719a8
Audit this contract →
← previous block
·
next block →
recent activity