pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,854,369
← previous block
next block →
recent activity
Analyzing
Block #94,854,369
11 transactions · 11 stateful · 2026-08-10 19:06:32 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,854,369
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
updateDataFeedsValuesPartial
#3
0x5acec890
#4
0x5acec890
#5
0x3f5c179b
#6
execFwdPositionOps
· blocks 1
#8
transferWithAuthorization
#9
transfer
#10
setData
#7
execFwdPositionOps
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
0x19795ad6…4a16
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf941a228…ec6f
0x34b655…2a6f
4 touches
1 conflict
0x1637d9f2…a9e5
0x34b655…2a6f
2 touches
0 conflicts
0x2acf7e76…bbe8
0x34b655…2a6f
2 touches
0 conflicts
0x4560e5a8…b741
0x34b655…2a6f
2 touches
0 conflicts
0x5eb187dd…b1d6
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
0x19795ad604…434a16
Audit this contract →
← previous block
·
next block →
recent activity