pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,789,086
← previous block
next block →
recent activity
Analyzing
Block #71,789,086
11 transactions · 9 stateful · 2026-05-01 19:12:01 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,789,086
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x69f4fb79
#4
0xeffdedb0
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x69f4fb79
#9
setData
#10
0x39435dac
#2
0x0c7abd22
· blocks 1
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x437cfa7e…b816
0x065c9d…c394
3 touches
1 conflict
0x1fa5c5b3…ff18
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x4029b728…e44d
0x065c9d…c394
2 touches
0 conflicts
0x5579724e…f943
0x065c9d…c394
2 touches
0 conflicts
0xc3006de0…9726
0x188d58…ea8e
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:
0x065c9d28…a9c394
1 conflict on slot
0x437cfa7eb2…94b816
Audit this contract →
← previous block
·
next block →
recent activity