pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,447,622
← previous block
next block →
recent activity
Analyzing
Block #96,447,622
9 transactions · 9 stateful · 2026-08-16 08:56:08 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,447,622
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute302
· blocks 1
#3
0x5acec890
#4
execOrders
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
setData
#2
execute302
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x446f2734…8b54
0x0a3323…0a3c
4 touches
1 conflict
0xff3addfc…633e
0x6f4756…dd5b
4 touches
1 conflict
0x52c63247…ce02
0x0a3323…0a3c
4 touches
1 conflict
0x00c43e68…2a3c
0x34b655…2a6f
2 touches
0 conflicts
0x26d8622c…e8af
0x34b655…2a6f
2 touches
0 conflicts
0x757b0543…e087
0x34b655…2a6f
2 touches
0 conflicts
0x833f3561…bfd0
0x34b655…2a6f
2 touches
0 conflicts
0x85a88798…f85e
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:
0x0a332311…6e0a3c
1 conflict on slot
0x446f273453…878b54
Audit this contract →
← previous block
·
next block →
recent activity