pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,145,784
← previous block
next block →
recent activity
Analyzing
Block #96,145,784
7 transactions · 7 stateful · 2026-08-15 07:38:04 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,145,784
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
dagSwapByOrderId
#3
setData
#4
execFwdPositionOpsV2
· blocks 1
#6
execOrders
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3c082c7…f032
0x34b655…2a6f
4 touches
1 conflict
0x5e8ddd73…4dfb
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x7467907b…964b
0x0a3323…0a3c
2 touches
0 conflicts
0xb1632c2f…d991
0x0a3323…0a3c
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
2 touches
0 conflicts
0x200ed648…912f
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
0xe3c082c74d…15f032
Audit this contract →
← previous block
·
next block →
recent activity