pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,568,229
← previous block
next block →
recent activity
Analyzing
Block #96,568,229
9 transactions · 6 stateful · 2026-08-16 19:03:03 UTC
Parallelism
78
/100
Blocked
33
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,568,229
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
0x008a1463
#5
execFwdPositionOpsV2
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#2
0x0c7abd22
#4
0xd60faa87
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1632c2f…d991
0x0a3323…0a3c
4 touches
1 conflict
0x63f5c02f…6853
0x3bd359…433a
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0x850662…52d0
4 touches
1 conflict
0x00000000…0004
0x850662…52d0
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:
0x0a332311…6e0a3c
1 conflict on slot
0xb1632c2f29…54d991
Audit this contract →
← previous block
·
next block →
recent activity