pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,280,867
← previous block
next block →
recent activity
Analyzing
Block #91,280,867
12 transactions · 10 stateful · 2026-07-29 07:11:45 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,280,867
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
setPrice
#2
0x6ad2e98b
#3
0x5a5d9a99
#4
0x5a5d9a99
#5
updateDataFeedsValuesPartial
#6
withdraw
#7
execFwdPositionOps
· blocks 1
#9
setData
#10
execFwdPositionOps
#11
0x6a69a829
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x022a0545…065a
0x34b655…2a6f
4 touches
1 conflict
0x71e39e15…640b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…642d
0x34b655…2a6f
4 touches
1 conflict
0xc8d59e0f…cfe0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x8e9077d3…a150
0x34b655…2a6f
3 touches
1 conflict
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
0x022a054589…0f065a
Audit this contract →
← previous block
·
next block →
recent activity