pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,022,976
← previous block
next block →
recent activity
Analyzing
Block #96,022,976
10 transactions · 8 stateful · 2026-08-14 21:20:18 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,022,976
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x4d8dc985
· blocks 2
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0xc9623387
#5
0x915df74d
#8
0xcffefd2e
#9
setData
#6
0xcffefd2e
#7
0xcffefd2e
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xdc0e94cb…c6d5
0x34b655…2a6f
4 touches
1 conflict
0xfd41f0ac…5252
0x34b655…2a6f
4 touches
1 conflict
0xffb2bfcf…b92a
0x34b655…2a6f
4 touches
1 conflict
0x08e8f2c9…a11a
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x00f7e3b7…e016
0x188d58…ea8e
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity