pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#117,049,330
← previous block
next block →
recent activity
Analyzing
Block #117,049,330
11 transactions · 10 stateful · 2026-10-27 13:07:54 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
#117,049,330
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
execPerpOps
#5
0xa96df62f
#6
execOrders
#7
setData
#8
0x84403c1b
· blocks 1
#10
0x57368ddf
#9
0x84403c1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f2dfe30…6e27
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x68c07cb9…ae14
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x46cb714c…a3d9
0x34b655…2a6f
2 touches
0 conflicts
0x49d4e4d8…72c3
0x34b655…2a6f
2 touches
0 conflicts
0x4bdc4b94…fc2c
0x34b655…2a6f
2 touches
0 conflicts
0x662bc9b5…26bd
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
0x2f2dfe30d0…bf6e27
Audit this contract →
← previous block
·
next block →
recent activity