pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,541,644
← previous block
next block →
recent activity
Analyzing
Block #92,541,644
12 transactions · 11 stateful · 2026-08-02 16:55:00 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,541,644
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
transfer
· blocks 1
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#7
placeAndExecuteMarketSell
#8
supply
#10
setData
#11
0x59558d29
#3
transfer
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5570577…8bf0
0x34b655…2a6f
4 touches
1 conflict
0x064a19b6…3f1d
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x78255c70…2733
0x34b655…2a6f
4 touches
1 conflict
0x78255c70…2734
0x34b655…2a6f
4 touches
1 conflict
0xc4e19ae4…0788
0xe7cd86…c82d
4 touches
1 conflict
0x1f02e5b0…3439
0x34b655…2a6f
2 touches
0 conflicts
0x259ed5f5…a86d
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
0xc55705778e…2f8bf0
Audit this contract →
← previous block
·
next block →
recent activity