pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,017,019
← previous block
next block →
recent activity
Analyzing
Block #91,017,019
11 transactions · 11 stateful · 2026-07-28 09:03:27 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,017,019
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 2
#5
execFwdPositionOps
#8
0x6a6870d6
#9
proposeResolution
#10
setData
#6
execFwdPositionOps
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
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
0xe22ab637…7a8e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x11435133…4bf8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x63cbfcc0…bb5c
0x34b655…2a6f
2 touches
0 conflicts
0x7b41d5cd…00e6
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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