pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,022,681
← previous block
next block →
recent activity
Analyzing
Block #95,022,681
11 transactions · 11 stateful · 2026-08-11 09:13:05 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,022,681
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
placeAndExecuteMarketSell
#3
updatePosition
#4
0x0c7abd22
#5
execFwdPositionOps
· blocks 1
#7
execute
#8
transfer
· blocks 1
#10
setData
#6
execFwdPositionOps
#9
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xabf57eb6…416d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x4981d48d…e2ef
0x34b655…2a6f
4 touches
1 conflict
0xff8d2106…6998
0x2a68ba…90c5
2 touches
0 conflicts
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0x3712eabf…edeb
0x6657d1…8ccc
2 touches
0 conflicts
0x54e1b3dd…2ec1
0x6657d1…8ccc
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
0xabf57eb66c…0a416d
Audit this contract →
← previous block
·
next block →
recent activity