pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,232,553
← previous block
next block →
recent activity
Analyzing
Block #93,232,553
11 transactions · 10 stateful · 2026-08-05 02:52:57 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,232,553
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
postPriceList
#2
execOrder
· blocks 1
#3
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
0x3f5c179b
#7
0xed82b078
#8
0x6a72a600
#9
transfer
#10
setData
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641d
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
2 touches
0 conflicts
0x183c10a3…2e0a
0x34b655…2a6f
2 touches
0 conflicts
0x1ab4c88c…49f2
0x34b655…2a6f
2 touches
0 conflicts
0x1de39dd7…f59a
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…af641f
Audit this contract →
← previous block
·
next block →
recent activity