pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,275,280
← previous block
next block →
recent activity
Analyzing
Block #91,275,280
10 transactions · 8 stateful · 2026-07-29 06:43:35 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,275,280
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#6
execFwdPositionOps
#7
0x57368ddf
#8
0x6a69a18f
#9
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa79d135a…76f2
0x34b655…2a6f
4 touches
1 conflict
0xc0eb79d1…29a4
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x03d53e11…3f6f
0x34b655…2a6f
2 touches
0 conflicts
0x072429df…ce94
0x34b655…2a6f
2 touches
0 conflicts
0x19530680…4c17
0x34b655…2a6f
2 touches
0 conflicts
0x26cb93fd…c15e
0x34b655…2a6f
2 touches
0 conflicts
0x913b7808…7e04
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
0xa79d135aeb…7d76f2
Audit this contract →
← previous block
·
next block →
recent activity