pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,643,123
← previous block
next block →
recent activity
Analyzing
Block #71,643,123
9 transactions · 9 stateful · 2026-05-01 02:59:44 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,643,123
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
· blocks 1
#2
updatePrices
#3
0xeffdedb0
#4
updateDataFeedsValuesPartial
#5
setData
#6
forward
#7
0x69f41797
#8
modifyLiquidities
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0dbf9688…c6cf
0xd18b7e…414b
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
0xe75ce681…ba5f
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba60
0x188d58…ea8e
2 touches
0 conflicts
0x17606ba6…1b6e
0x754704…b603
2 touches
0 conflicts
0x1a0c3cc5…6c5a
0x754704…b603
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:
0xd18b7ec5…10414b
1 conflict on slot
0x0dbf9688de…b0c6cf
Audit this contract →
← previous block
·
next block →
recent activity