pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#71,094,378
← previous block
next block →
recent activity
Analyzing
Block #71,094,378
11 transactions · 10 stateful · 2026-04-28 14:01:20 UTC
Parallelism
64
/100
Blocked
30
%
Avg conflicts / tx
0.36
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,094,378
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
trade
#5
updatePrices
#7
updateDataFeedsValuesPartial
#8
forward
#9
commit
#10
setData
#2
0x0c7abd22
· blocks 2
#4
execute
· blocks 1
#6
0xce1e7030
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
6
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x8876d94c…8435
0x2a68ba…90c5
4 touches
1 conflict
0x03f9cc30…b465
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x51a23bf3…8824
0xd32edf…ff58
3 touches
1 conflict
0xb5a508af…ddce
0xa6afd3…d132
3 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
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:
0x754704bc…afb603
3 conflicts on slot
0x17606ba612…ea1b6e
Audit this contract →
← previous block
·
next block →
recent activity