pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,356,449
← previous block
next block →
recent activity
Analyzing
Block #95,356,449
10 transactions · 10 stateful · 2026-08-12 13:24:11 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,356,449
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#4
repayWithCollateral
#5
0x3f5c179b
#6
0x6a7c7473
#7
transfer
#8
setData
#9
0x59558d29
#2
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67a56c8b…f955
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
2 touches
0 conflicts
0x098db796…75a4
0x34b655…2a6f
2 touches
0 conflicts
0x3c955e7e…ef5e
0x34b655…2a6f
2 touches
0 conflicts
0x4abaedb1…65b9
0x34b655…2a6f
2 touches
0 conflicts
0x4f1b7b03…17fd
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
0x67a56c8b2e…d7f955
Audit this contract →
← previous block
·
next block →
recent activity