pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,461,015
← previous block
next block →
recent activity
Analyzing
Block #92,461,015
13 transactions · 12 stateful · 2026-08-02 10:09:27 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,461,015
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrder
· blocks 1
#3
withdraw
#4
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
0x94defb17
· blocks 1
#9
execOrders
#10
0x6a6f17cf
#11
setData
#12
0x59558d29
#5
execFwdPositionOps
#8
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55c5b153…97cf
0x968279…9342
4 touches
1 conflict
0x0f648dec…85d6
0x968279…9342
4 touches
1 conflict
0x0f648dec…85d7
0x968279…9342
4 touches
1 conflict
0x0f648dec…85d9
0x968279…9342
4 touches
1 conflict
0x55c5b153…97c8
0x968279…9342
4 touches
1 conflict
0x55c5b153…97c9
0x968279…9342
4 touches
1 conflict
0x55c5b153…97cc
0x968279…9342
4 touches
1 conflict
0x55c5b153…97cd
0x968279…9342
4 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:
0x96827978…f09342
1 conflict on slot
0x55c5b153ab…9997cf
Audit this contract →
← previous block
·
next block →
recent activity