pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,436,774
← previous block
next block →
recent activity
Analyzing
Block #96,436,774
10 transactions · 9 stateful · 2026-08-16 08:01:35 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,436,774
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x5acec890
#3
permit2TransferAndMulticall
· blocks 1
#5
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
#8
updateDataFeedsValuesPartial
#9
setData
#4
permit2TransferAndMulticall
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x1c8a33…d316
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x48b13e5e…3c2a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x856d36e4…f467
0x5a66a5…cba8
4 touches
1 conflict
0x00000000…0003
0x98a45d…206a
4 touches
1 conflict
0xaeb46f64…7cfc
0xaca92e…35da
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:
0x1c8a3360…efd316
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity