pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,414,643
← previous block
next block →
recent activity
Analyzing
Block #95,414,643
11 transactions · 10 stateful · 2026-08-12 18:18:47 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,414,643
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
0x3f5c179b
#4
execFwdPositionOps
#5
forward
#6
execFwdPositionOps
· blocks 1
#7
setData
· blocks 1
#9
0x59558d29
#8
setData
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w0
8
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xe9452241…95a3
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x6676e87f…b88f
0x2a68ba…90c5
2 touches
0 conflicts
0xdaf4f143…58d4
0x2a68ba…90c5
2 touches
0 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
2 touches
0 conflicts
0x1a04fff3…c30a
0x34b655…2a6f
2 touches
0 conflicts
0x1f81743e…117b
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:
0x33176be2…ede078
1 conflict on slot
0x09106a952c…111467
Audit this contract →
← previous block
·
next block →
recent activity