pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,209,079
← previous block
next block →
recent activity
Analyzing
Block #96,209,079
9 transactions · 5 stateful · 2026-08-15 12:56:24 UTC
Parallelism
78
/100
Blocked
20
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,209,079
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execOrders
#3
0x8ef791…154c
#4
0xf92049…2a5f
#5
setData
#6
0x61d59c2d
#7
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x200ed648…912f
0x34b655…2a6f
4 touches
1 conflict
0x840175ed…af51
0x34b655…2a6f
4 touches
1 conflict
0x2749d514…3067
0x34b655…2a6f
4 touches
1 conflict
0xbb44cedd…c666
0x34b655…2a6f
4 touches
1 conflict
0xc8573606…e6d1
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdfe311f9…a651
0x34b655…2a6f
4 touches
1 conflict
0xe732567d…b65d
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x200ed6482b…21912f
Audit this contract →
← previous block
·
next block →
recent activity