pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,157,797
← previous block
next block →
recent activity
Analyzing
Block #96,157,797
9 transactions · 8 stateful · 2026-08-15 08:38:29 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,157,797
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0xcffefd2e
#5
0x57368ddf
#6
setData
#7
0x39435dac
· blocks 1
#2
0x39435dac
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99ebc4d…22f9
0x34b655…2a6f
4 touches
1 conflict
0x9895e7db…8035
0x34b655…2a6f
4 touches
1 conflict
0xa1571d54…ae41
0x34b655…2a6f
4 touches
1 conflict
0xbbb9fa77…d121
0x34b655…2a6f
4 touches
1 conflict
0xcedd9c7b…916e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe73b93bf…c0e1
0x34b655…2a6f
4 touches
1 conflict
0x16f8e14a…f6e4
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xe99ebc4d01…5b22f9
Audit this contract →
← previous block
·
next block →
recent activity