pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,855,552
← previous block
next block →
recent activity
Analyzing
Block #93,855,552
11 transactions · 10 stateful · 2026-08-07 07:05:01 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,855,552
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execPerpOps
#3
execPerpOps
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
0x57368ddf
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x918934b6…41d4
0x34b655…2a6f
4 touches
1 conflict
0x6ac4a9ce…5f63
0x34b655…2a6f
4 touches
1 conflict
0x437104d2…66a2
0x34b655…2a6f
4 touches
1 conflict
0xfbe6a366…8ca1
0x34b655…2a6f
4 touches
1 conflict
0x0eac7709…66c3
0x34b655…2a6f
2 touches
0 conflicts
0x342222e8…2ec4
0x34b655…2a6f
2 touches
0 conflicts
0x3a7091da…f2eb
0x34b655…2a6f
2 touches
0 conflicts
0x46870010…0b51
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
0x918934b624…fc41d4
Audit this contract →
← previous block
·
next block →
recent activity