pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,743,849
← previous block
next block →
recent activity
Analyzing
Block #71,743,849
10 transactions · 9 stateful · 2026-05-01 14:10:24 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,743,849
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9036287a
· blocks 1
#2
updatePrices
#3
0xeffdedb0
#5
0x69f4b4c7
#6
setData
#7
strike
#8
0x39435dac
#9
modifyLiquidities
#4
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x888665f1…db67
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb63b9f2c…28e8
0x065c9d…c394
3 touches
1 conflict
0x29021edc…5b89
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
0x065c9d…c394
2 touches
0 conflicts
0x508387de…c644
0x2a68ba…90c5
2 touches
0 conflicts
0x0175b7a6…1dbc
0x33663b…4897
2 touches
0 conflicts
0x0175b7a6…1dbd
0x33663b…4897
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
0x888665f118…83db67
Audit this contract →
← previous block
·
next block →
recent activity