pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,648,115
← previous block
next block →
recent activity
Analyzing
Block #71,648,115
11 transactions · 8 stateful · 2026-05-01 03:32:54 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,648,115
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f41f5e
#2
postPrice
#3
execute
#4
swap
#5
0xeffdedb0
#6
setData
#7
updateDataFeedsValuesPartial
#8
0x69f41f5e
#9
0x39435dac
· blocks 1
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x00000000…0005
0x2a3755…a5a6
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
0x801a6e5726…c1d85c
Audit this contract →
← previous block
·
next block →
recent activity