pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,867,688
← previous block
next block →
recent activity
Analyzing
Block #92,867,688
12 transactions · 11 stateful · 2026-08-03 20:16:23 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,867,688
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
execFwdPositionOps
· blocks 1
#6
0x3f5c179b
#8
transfer
· blocks 1
#10
setData
#11
0x59558d29
#7
execFwdPositionOps
#9
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92b49f44…ee4f
0x34b655…2a6f
4 touches
1 conflict
0x154b56c6…3d64
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x3f152ba8…cea6
0x34b655…2a6f
2 touches
0 conflicts
0x55053821…73e4
0x34b655…2a6f
2 touches
0 conflicts
0x5aa29d18…83c7
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
0x92b49f44ef…78ee4f
Audit this contract →
← previous block
·
next block →
recent activity