pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,558,304
← previous block
next block →
recent activity
Analyzing
Block #71,558,304
9 transactions · 9 stateful · 2026-04-30 17:35:16 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,558,304
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xeffdedb0
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
setData
#5
updateDataFeedsValuesPartial
#6
claimRewards
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfca3cd0…5023
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
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
2 touches
0 conflicts
0x0fc41e7b…6831
0x98dc6e…8633
2 touches
0 conflicts
0x5b571ba0…f13a
0x98dc6e…8633
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
0xbfca3cd067…cd5023
Audit this contract →
← previous block
·
next block →
recent activity