pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,157,866
← previous block
next block →
recent activity
Analyzing
Block #91,157,866
7 transactions · 6 stateful · 2026-07-28 20:52:08 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,157,866
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 1
#3
0x0f6795d9
#5
setData
#6
0xc7e3ec2c
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d0bf98a…b467
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0aa5e418…5d1d
0x34b655…2a6f
2 touches
0 conflicts
0x0da3714e…3e97
0x34b655…2a6f
2 touches
0 conflicts
0x157dbfb2…4089
0x34b655…2a6f
2 touches
0 conflicts
0x1951d7ce…497d
0x34b655…2a6f
2 touches
0 conflicts
0x1b9b64a4…9a31
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
0x8d0bf98a07…cbb467
Audit this contract →
← previous block
·
next block →
recent activity