pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,858,357
← previous block
next block →
recent activity
Analyzing
Block #94,858,357
9 transactions · 8 stateful · 2026-08-10 19:26:35 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,858,357
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x8263f5d9
#2
updatePrices
#3
0x5acec890
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
0x0f6795d9
· blocks 1
#8
setData
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x183c10a3…2e0a
0x34b655…2a6f
2 touches
0 conflicts
0x2877f440…c2c8
0x34b655…2a6f
2 touches
0 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
2 touches
0 conflicts
0x3643741b…109c
0x34b655…2a6f
2 touches
0 conflicts
0x545e527e…0eb0
0x34b655…2a6f
2 touches
0 conflicts
0x5a6864fe…2890
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:
Perpl
1 conflict on slot
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity