pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,959,538
← previous block
next block →
recent activity
Analyzing
Block #92,959,538
10 transactions · 10 stateful · 2026-08-04 03:58:30 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,959,538
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
updateDataFeedsValuesPartial
#3
execOrders
· blocks 1
#5
batchUpdatePrice
#6
setData
#7
execOrders
· blocks 1
#9
0xc7e3ec2c
#4
execFwdPositionOps
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa56e54d0…2d39
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x120847e2…98c2
0x34b655…2a6f
4 touches
1 conflict
0x16d18a86…d884
0x34b655…2a6f
4 touches
1 conflict
0x0140fbd3…d957
0x34b655…2a6f
4 touches
1 conflict
0xd31f6e25…18da
0x34b655…2a6f
4 touches
1 conflict
0xd4702f73…926c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
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
0xa56e54d018…f82d39
Audit this contract →
← previous block
·
next block →
recent activity