pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,243,805
← previous block
next block →
recent activity
Analyzing
Block #92,243,805
12 transactions · 10 stateful · 2026-08-01 15:57:05 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,243,805
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#5
execOrders
#7
updateDataFeedsValuesPartial
#8
0xe9316489
#9
setData
#10
updatePrices
#11
0xc7e3ec2c
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc684438…8bc3
0x34b655…2a6f
4 touches
1 conflict
0x35b89cd8…5092
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x07d94be1…7fa8
0x34b655…2a6f
2 touches
0 conflicts
0x2ace2029…e9ad
0x34b655…2a6f
2 touches
0 conflicts
0x2dd03fb9…6243
0x34b655…2a6f
2 touches
0 conflicts
0x327c57dd…836d
0x34b655…2a6f
2 touches
0 conflicts
0x44f26cbe…58c2
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
0xbc684438a0…3d8bc3
Audit this contract →
← previous block
·
next block →
recent activity