pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,161,906
← previous block
next block →
recent activity
Analyzing
Block #95,161,906
8 transactions · 7 stateful · 2026-08-11 20:54:12 UTC
Parallelism
63
/100
Blocked
43
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,161,906
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x4d8dc985
· blocks 1
#3
updateDataFeedsValuesPartial
#6
setData
· blocks 1
#4
0x0f6795d9
· blocks 1
#7
setData
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w2
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbadf6b0…43b2
0x33176b…e078
4 touches
1 conflict
0x679705f0…4531
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfadc118d…5d64
0x34b655…2a6f
4 touches
1 conflict
0xa3ff1ab2…8ae3
0x34b655…2a6f
4 touches
1 conflict
0x7bc81250…725f
0x34b655…2a6f
2 touches
0 conflicts
0x82a21578…a099
0x34b655…2a6f
2 touches
0 conflicts
0x949fc5d9…55f3
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:
0x33176be2…ede078
1 conflict on slot
0xdbadf6b093…d843b2
Audit this contract →
← previous block
·
next block →
recent activity