pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,906,092
← previous block
next block →
recent activity
Analyzing
Block #91,906,092
10 transactions · 10 stateful · 2026-07-31 11:38:35 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,906,092
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
forward
#2
0x7d2c3ba9
#3
execFwdPositionOps
· blocks 2
#6
setData
#7
0x59558d29
#8
0xc7e3ec2c
#9
0xc7e3ec2c
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xef79589c…0088
0x34b655…2a6f
4 touches
1 conflict
0x706c758c…2fdb
0x34b655…2a6f
4 touches
1 conflict
0x49c921c1…4ff7
0x000000…012a
2 touches
0 conflicts
0xe7fa6db5…a6d4
0x000000…012a
2 touches
0 conflicts
0x00000000…000b
0x24f29b…4337
2 touches
0 conflicts
0xabbb5caa…a569
0x2f7a86…c9c4
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity