pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,403,866
← previous block
next block →
recent activity
Analyzing
Block #91,403,866
11 transactions · 8 stateful · 2026-07-29 17:30:48 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,403,866
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
updateDataFeedsValuesPartial
#4
executeBatch
#5
execFwdPositionOps
#6
0x8f7799…f3ad
#7
0xe5eb7c…1596
#8
setData
#9
0x59558d29
#10
0xc7e3ec2c
#2
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32b7e349…5f63
0x34b655…2a6f
4 touches
1 conflict
0x5a08ca7f…6546
0x34b655…2a6f
4 touches
1 conflict
0xbcdd58ff…0711
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x103f63b2…ff11
0x34b655…2a6f
2 touches
0 conflicts
0x103f63b2…ff12
0x34b655…2a6f
2 touches
0 conflicts
0x1b317ce5…002f
0x34b655…2a6f
2 touches
0 conflicts
0x20081203…b191
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
0x32b7e34965…585f63
Audit this contract →
← previous block
·
next block →
recent activity