pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,266,489
← previous block
next block →
recent activity
Analyzing
Block #91,266,489
10 transactions · 8 stateful · 2026-07-29 05:58:39 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,266,489
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6ad2e98b
· blocks 2
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
execFwdPositionOps
#8
execFwdPositionOps
#9
setData
#6
0x3f5c179b
· blocks 1
#7
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3406c63…f416
0x851145…3f07
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x010bab9f…6b7e
0x851145…3f07
6 touches
3 conflicts
0x8f825eeb…9942
0x851145…3f07
6 touches
3 conflicts
0x1d4eb322…2f6e
0x851145…3f07
4 touches
1 conflict
0x4e6be409…6e20
0x851145…3f07
3 touches
1 conflict
0x7bd11ee0…707a
0x851145…3f07
3 touches
1 conflict
0x9b22c356…15a2
0x851145…3f07
3 touches
1 conflict
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:
0x851145ea…9f3f07
3 conflicts on slot
0xd3406c6375…dff416
Audit this contract →
← previous block
·
next block →
recent activity