pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,743,104
← previous block
next block →
recent activity
Analyzing
Block #71,743,104
12 transactions · 10 stateful · 2026-05-01 14:05:25 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,743,104
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updatePrices
· blocks 1
#4
updatePrices
#5
0xeffdedb0
#6
updateDataFeedsValuesPartial
#7
0xb139e5…a04f
#9
0x69f4b39c
#10
setData
#11
0x39435dac
#3
updatePrices
#8
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6254f674…face
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0x246f1be6…5aae
0x065c9d…c394
3 touches
1 conflict
0xa93201f2…92f5
0x065c9d…c394
3 touches
1 conflict
0xfe51d2c4…3d4b
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity