pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,575,150
← previous block
next block →
recent activity
Analyzing
Block #95,575,150
10 transactions · 10 stateful · 2026-08-13 07:46:19 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
#95,575,150
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
execOrders
· blocks 1
#3
updatePrices
#5
execFwdPositionOps
#6
0x94defb17
· blocks 1
#8
transfer
#9
setData
#4
execFwdPositionOps
#7
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86be13e3…50e5
0x968279…9342
4 touches
1 conflict
0x0027e0db…a104
0x968279…9342
4 touches
1 conflict
0x0027e0db…a105
0x968279…9342
4 touches
1 conflict
0x0027e0db…a108
0x968279…9342
4 touches
1 conflict
0x0027e0db…a109
0x968279…9342
4 touches
1 conflict
0x0027e0db…a10a
0x968279…9342
4 touches
1 conflict
0x86be13e3…50e2
0x968279…9342
4 touches
1 conflict
0x86be13e3…50e3
0x968279…9342
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:
0x96827978…f09342
1 conflict on slot
0x86be13e3d5…aa50e5
Audit this contract →
← previous block
·
next block →
recent activity