pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,176,717
← previous block
next block →
recent activity
Analyzing
Block #71,176,717
14 transactions · 13 stateful · 2026-04-28 23:09:43 UTC
Parallelism
79
/100
Blocked
31
%
Avg conflicts / tx
0.29
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,176,717
· 14 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute_route
· blocks 2
#3
0x69f13eaf
#6
updatePrices
#7
postPrice
#8
0x98717539
· blocks 1
#9
0x6463ffd1
#10
setData
#11
forward
#12
0x69f13eaf
#2
execute_route
· blocks 1
#5
exactOutputSingle
#13
0x39435dac
#4
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
5
w1
8
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c49c85c…ee96
0x34b655…2a6f
4 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0x18aed20c…48f3
0x000000…012a
4 touches
1 conflict
0x00000000…0000
0xd5b70d…615b
4 touches
1 conflict
0x00000000…0002
0xd5b70d…615b
4 touches
1 conflict
0x00000000…0004
0xd5b70d…615b
4 touches
1 conflict
0x113e9920…5e90
0x000000…012a
3 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
0x8c49c85c3e…afee96
Audit this contract →
← previous block
·
next block →
recent activity