pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,489,771
← previous block
next block →
recent activity
Analyzing
Block #84,489,771
11 transactions · 7 stateful · 2026-06-29 15:17:24 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,489,771
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
withdraw
#4
0x0f6795d9
#5
0x0f6795d9
· blocks 1
#6
setData
#7
0x32366535
#8
0x39435dac
#10
0xc7e3ec2c
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00e21a9f…3583
0x34b655…2a6f
2 touches
0 conflicts
0x134ea5b5…4601
0x34b655…2a6f
2 touches
0 conflicts
0x1ff965a5…b3aa
0x34b655…2a6f
2 touches
0 conflicts
0x26c9c9b3…b62f
0x34b655…2a6f
2 touches
0 conflicts
0x454d8940…cfe7
0x34b655…2a6f
2 touches
0 conflicts
0x5d4a3441…e31c
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity