pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,301,884
← previous block
next block →
recent activity
Analyzing
Block #92,301,884
8 transactions · 7 stateful · 2026-08-01 20:49:12 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,301,884
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
placeAndExecuteMarketSell
· blocks 1
#4
execFwdPositionOps
#5
setData
#6
0x59558d29
#7
0xc7e3ec2c
#3
placeAndExecuteMarketSell
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31bf04b6…3fd0
0x40c49f…2af0
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x6518075e…2b17
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x2bb0d58d…9dcf
0x34b655…2a6f
2 touches
0 conflicts
0x41ee4f8f…d065
0x34b655…2a6f
2 touches
0 conflicts
0x9a8af3c2…e4ae
0x34b655…2a6f
2 touches
0 conflicts
0xb839a1e8…22b3
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:
0x40c49f17…d22af0
1 conflict on slot
0x31bf04b611…723fd0
Audit this contract →
← previous block
·
next block →
recent activity