pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#104,201,499
← previous block
next block →
recent activity
Analyzing
Block #104,201,499
10 transactions · 8 stateful · 2026-09-12 14:19:06 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#104,201,499
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x59558d29
#3
0x59558d29
#4
execPerpOps
#5
execPerpOps
#6
execFwdPositionOpsV2
· blocks 1
#8
execFwdPositionOpsV2
#9
setData
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x168f7615…a8de
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0ec5a1b3…54d4
0x34b655…2a6f
2 touches
0 conflicts
0x0ec5a1b3…54d5
0x34b655…2a6f
2 touches
0 conflicts
0x1408e7c7…f324
0x34b655…2a6f
2 touches
0 conflicts
0x27754bd4…96ae
0x34b655…2a6f
2 touches
0 conflicts
0x42522e76…2592
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
0x168f7615e7…68a8de
Audit this contract →
← previous block
·
next block →
recent activity