pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,219,489
← previous block
next block →
recent activity
Analyzing
Block #96,219,489
8 transactions · 7 stateful · 2026-08-15 13:48:45 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,219,489
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOpsV2
· blocks 1
#2
execFwdPositionOpsV2
#3
executeBatch
#4
execOrders
#6
0x8b80a919
#7
setData
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x08e8f2c9…a11a
0x34b655…2a6f
2 touches
0 conflicts
0x3270f906…a0e9
0x34b655…2a6f
2 touches
0 conflicts
0x424934c8…f2f1
0x34b655…2a6f
2 touches
0 conflicts
0x47527bb5…0071
0x34b655…2a6f
2 touches
0 conflicts
0x513b0c80…d2d9
0x34b655…2a6f
2 touches
0 conflicts
0x5427efe9…f9f3
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
0xafb8e71eb0…ec9285
Audit this contract →
← previous block
·
next block →
recent activity