pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,701,611
← previous block
next block →
recent activity
Analyzing
Block #71,701,611
8 transactions · 7 stateful · 2026-05-01 09:29:03 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,701,611
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x1a945f9c
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x69f472d7
#7
setData
#3
0xd10227eb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6b74ae0…8d5e
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0xaca0e789…9b35
0xfd44b3…00d1
4 touches
1 conflict
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x24e279c2…cf29
0x1efe02…37d6
2 touches
0 conflicts
0x9250ec46…1329
0x1efe02…37d6
2 touches
0 conflicts
0xa5a6f1ab…8573
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:
0xea1b8e4a…8fc5ec
1 conflict on slot
0xb6b74ae0ff…d48d5e
Audit this contract →
← previous block
·
next block →
recent activity