pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,203,360
← previous block
next block →
recent activity
Analyzing
Block #92,203,360
8 transactions · 6 stateful · 2026-08-01 12:33:41 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,203,360
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
· blocks 1
#6
execOrders
#7
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a42683d…6f50
0x34b655…2a6f
4 touches
1 conflict
0x7bb6e9d0…1dbd
0x34b655…2a6f
4 touches
1 conflict
0x7bc132c6…0dd8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0a42683d…6f4f
0x34b655…2a6f
4 touches
1 conflict
0x24b6091e…d294
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x3a5d6372…34cd
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x0a42683dda…f36f50
Audit this contract →
← previous block
·
next block →
recent activity