pev
.
One block, wave by wave
→
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#81,623,427
← previous block
next block →
recent activity
Analyzing
Block #81,623,427
11 transactions · 8 stateful · 2026-06-16 08:28:31 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,623,427
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
addLiquidity
#5
forward
#6
forward
#7
0x6a3109a7
#8
setData
#9
0x39435dac
· blocks 1
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49535ffa…02e8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe09c8417…8c91
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x033d8128…5def
0x5afd3e…7620
2 touches
0 conflicts
0x0df99e9a…a200
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
2 touches
0 conflicts
0x3378e8b6…20a9
0x754704…b603
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
0x49535ffafc…cd02e8
Audit this contract →
← previous block
·
next block →
recent activity