pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,811,546
← previous block
next block →
recent activity
Analyzing
Block #91,811,546
11 transactions · 10 stateful · 2026-07-31 03:42:52 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,811,546
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execFwdPositionOps
· blocks 2
#3
execFwdPositionOps
· blocks 1
#5
execOrders
#6
0x6a6c1a34
#7
setData
#9
0x59558d29
#10
0xc7e3ec2c
#4
execFwdPositionOps
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x961c0cd9…0937
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf28a9fc2…05e4
0x34b655…2a6f
4 touches
1 conflict
0xfed09e59…a493
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x1321736a…43e3
0x34b655…2a6f
2 touches
0 conflicts
0x1d6cb721…c88c
0x34b655…2a6f
2 touches
0 conflicts
0x208c752c…2cd4
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
0x961c0cd92c…d10937
Audit this contract →
← previous block
·
next block →
recent activity