pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,797,962
← previous block
next block →
recent activity
Analyzing
Block #91,797,962
8 transactions · 8 stateful · 2026-07-31 02:34:31 UTC
Parallelism
25
/100
Blocked
63
%
Avg conflicts / tx
1.88
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,797,962
· 8 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
execOrder
· blocks 5
#7
setData
#2
execOrder
· blocks 4
#3
execOrder
· blocks 3
#4
execFwdPositionOps
· blocks 2
#5
execFwdPositionOps
· blocks 1
#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
w3
5
w4
6
w5
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x744138db…a855
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xfed09e59…a493
0x34b655…2a6f
10 touches
10 conflicts
0x4bfdcd51…9b58
0x34b655…2a6f
8 touches
6 conflicts
0x8f63f383…6eda
0x34b655…2a6f
6 touches
3 conflicts
0x0a6f5e37…6c3c
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot
0x744138db0a…e7a855
Audit this contract →
← previous block
·
next block →
recent activity