pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,566,098
← previous block
next block →
recent activity
Analyzing
Block #96,566,098
13 transactions · 5 stateful · 2026-08-16 18:52:20 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,566,098
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x4f819052
· blocks 1
#2
0x00a41485
#3
0xaf5e395a
#4
0x50a0b275
#6
main_all
#7
0x0c7abd22
#8
0x62be7533
#9
updateDataFeedsValuesPartial
#10
setData
#11
execFwdPositionOpsV2
#12
execFwdPositionOpsV2
#5
main_all
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x850662…52d0
4 touches
1 conflict
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…0002
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
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:
0x8506627b…b052d0
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity