pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,555,740
← previous block
next block →
recent activity
Analyzing
Block #71,555,740
10 transactions · 9 stateful · 2026-04-30 17:18:08 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,555,740
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
0xeffdedb0
#4
0x1a945f9c
· blocks 1
#5
updatePosition
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
#6
0x366fe5db
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x52b4626e…9e5a
0x1efe02…37d6
2 touches
0 conflicts
0xdd0b4c6e…13b4
0x1efe02…37d6
2 touches
0 conflicts
0xdee3761a…e18c
0x1efe02…37d6
2 touches
0 conflicts
0x00000000…0002
0x7e9d3a…9fda
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:
0xfd44b351…7f00d1
1 conflict on slot
0x00bac0131a…bba28c
Audit this contract →
← previous block
·
next block →
recent activity