pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,435,015
← previous block
next block →
recent activity
Analyzing
Block #91,435,015
10 transactions · 10 stateful · 2026-07-29 20:08:41 UTC
Parallelism
70
/100
Blocked
40
%
Avg conflicts / tx
0.6
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,435,015
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 2
#4
execFwdPositionOps
· blocks 2
#7
0x6a6a5e40
#8
setData
#9
0x59558d29
#2
updatePrices
· blocks 1
#5
execFwdPositionOps
· blocks 1
#3
updatePrices
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0xa1980c71…f097
0x34b655…2a6f
4 touches
1 conflict
0x09676b1b…9044
0x34b655…2a6f
2 touches
0 conflicts
0x19e3ac37…88ac
0x34b655…2a6f
2 touches
0 conflicts
0x1b26abd1…d755
0x34b655…2a6f
2 touches
0 conflicts
0x1c3295fd…097a
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
3 conflicts on slot
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity