pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,778,365
← previous block
next block →
recent activity
Analyzing
Block #91,778,365
17 transactions · 11 stateful · 2026-07-31 00:55:57 UTC
Parallelism
88
/100
Blocked
27
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,778,365
· 17 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x0c7abd22
· blocks 1
#3
0x0c7abd22
#5
0x0c7abd22
#6
0x5a5d9a99
#7
execFwdPositionOps
#8
execFwdPositionOps
· blocks 1
#10
updateDataFeedsValuesPartial
#11
0x3f5c179b
#12
execOrders
#13
execOrders
#14
execOrders
#15
setData
· blocks 1
#4
0x0c7abd22
#9
execFwdPositionOps
#16
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
8
w0
9
w1
15
w0
16
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7e1faa73…bfbf
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x725c87d9…95f5
0xd32edf…ff58
3 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002e
0x1b6862…e19c
2 touches
0 conflicts
0xd5b10148…e637
0x1b6862…e19c
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
0x09106a952c…111467
Audit this contract →
← previous block
·
next block →
recent activity