pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,387,059
← previous block
next block →
recent activity
Analyzing
Block #96,387,059
9 transactions · 9 stateful · 2026-08-16 03:51:34 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,387,059
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
updateDataFeedsValuesPartial
#4
execFwdPositionOpsV2
#5
0xb2d4797b
#6
forward
#7
forward
#8
setData
#3
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73670e81…2813
0x34b655…2a6f
4 touches
1 conflict
0x4524306a…1098
0x34b655…2a6f
4 touches
1 conflict
0xee6cbe65…9541
0x34b655…2a6f
4 touches
1 conflict
0xf1faa605…f919
0x34b655…2a6f
4 touches
1 conflict
0x3a7f96df…f31e
0x34b655…2a6f
2 touches
0 conflicts
0x48a0f121…953b
0x34b655…2a6f
2 touches
0 conflicts
0x68297b76…8e24
0x34b655…2a6f
2 touches
0 conflicts
0x74fd0a9b…3aaa
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
0x73670e81ae…572813
Audit this contract →
← previous block
·
next block →
recent activity