pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,555,196
← previous block
next block →
recent activity
Analyzing
Block #95,555,196
12 transactions · 12 stateful · 2026-08-13 06:05:58 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,555,196
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
matchOrders
#3
updatePrices
#4
0xab083028
#5
execOrder
· blocks 1
#8
0x6a7d5f3d
#9
execFwdPositionOps
#10
setData
#11
execOrders
#6
execOrder
· blocks 1
#7
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d5e476…8a1f
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x468609cb…76b1
0x065c9d…c394
2 touches
0 conflicts
0xb33ff823…1188
0x065c9d…c394
2 touches
0 conflicts
0xc3ecbd6f…46ed
0x065c9d…c394
2 touches
0 conflicts
0xccee6cc7…0e3e
0x065c9d…c394
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
0x66d5e476c0…268a1f
Audit this contract →
← previous block
·
next block →
recent activity