pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,525,410
← previous block
next block →
recent activity
Analyzing
Block #92,525,410
10 transactions · 10 stateful · 2026-08-02 15:33:22 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,525,410
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
updatePosition
#6
0x3f5c179b
#7
setData
#8
execOrders
#9
0x59558d29
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda48aa08…f99e
0x34b655…2a6f
4 touches
1 conflict
0xbdc80bf7…e947
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x4188cc5f…2d2e
0x34b655…2a6f
2 touches
0 conflicts
0x84ee6168…3f13
0x34b655…2a6f
2 touches
0 conflicts
0x84ee6168…3f14
0x34b655…2a6f
2 touches
0 conflicts
0xa4e9800f…4ab1
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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
0xda48aa08a7…73f99e
Audit this contract →
← previous block
·
next block →
recent activity