pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,326,027
← previous block
next block →
recent activity
Analyzing
Block #92,326,027
9 transactions · 9 stateful · 2026-08-01 22:50:38 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,326,027
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#5
execFwdPositionOps
#6
exec
#7
0x6a6e78b5
#8
setData
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc1e16402…a780
0x34b655…2a6f
4 touches
1 conflict
0x06a105dc…0b66
0x34b655…2a6f
2 touches
0 conflicts
0x13a157e0…215b
0x34b655…2a6f
2 touches
0 conflicts
0x21605a79…d719
0x34b655…2a6f
2 touches
0 conflicts
0x2a77f8f7…f6b3
0x34b655…2a6f
2 touches
0 conflicts
0x3115496a…f3a1
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity