pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,743,345
← previous block
next block →
recent activity
Analyzing
Block #71,743,345
10 transactions · 9 stateful · 2026-05-01 14:07:01 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,743,345
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#4
updatePrices
#5
0xeffdedb0
#6
0x3f5c179b
#7
updateDataFeedsValuesPartial
#8
0x69f4b3fd
#9
setData
#2
0x0c7abd22
· blocks 1
#3
0x9609049f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c2eb62e…b7ca
0x065c9d…c394
6 touches
3 conflicts
0x438cf5f6…f077
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x21d8e673…067e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x6ca627d9…d1fc
0xd32edf…ff58
3 touches
1 conflict
0x0bcaba7e…0e80
0x3bd359…433a
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
3 conflicts on slot
0x1c2eb62e6e…c1b7ca
Audit this contract →
← previous block
·
next block →
recent activity