pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,239,235
← previous block
next block →
recent activity
Analyzing
Block #71,239,235
10 transactions · 9 stateful · 2026-04-29 06:05:34 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,239,235
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
_makeSwaps
· blocks 1
#2
0x69f1a026
#3
updateDataFeedsValuesPartial
#4
0x785f5745
#5
0x6463ffd1
#6
setData
#7
updatePriceFeedsIfNecessary
#9
0x39435dac
#8
0x0c7abd22
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
0xa4e3b3b1…0911
0x2a68ba…90c5
4 touches
1 conflict
0x0593c7d0…e448
0xa6afd3…d132
3 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
0x8edd456e…c7e3
0x0555e3…2b9c
2 touches
0 conflicts
0xee0a9ebb…c425
0x0555e3…2b9c
2 touches
0 conflicts
0x00000000…0000
0x2b37ef…0bdc
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:
0x2a68ba18…8e90c5
1 conflict on slot
0xa4e3b3b1bb…130911
Audit this contract →
← previous block
·
next block →
recent activity