pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,525,679
← previous block
next block →
recent activity
Analyzing
Block #96,525,679
9 transactions · 7 stateful · 2026-08-16 15:29:03 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,525,679
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
execOrders
#3
0x05c0fc…a76a
#4
execFwdPositionOpsV2
· blocks 1
#6
setData
#7
0x0c7abd22
#8
forward
#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
0xa46242d8…c0a7
0x34b655…2a6f
4 touches
1 conflict
0x4c98b4d5…c6ad
0x34b655…2a6f
4 touches
1 conflict
0xb7fb66e8…4f94
0x34b655…2a6f
4 touches
1 conflict
0x56a284d9…32e4
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x46ee3c65…4ab8
0x34b655…2a6f
3 touches
1 conflict
0x75a69dd9…8f57
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
0xa46242d871…37c0a7
Audit this contract →
← previous block
·
next block →
recent activity