pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,423,955
← previous block
next block →
recent activity
Analyzing
Block #91,423,955
7 transactions · 7 stateful · 2026-07-29 19:12:14 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,423,955
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39abec6b
#2
execFwdPositionOps
· blocks 1
#4
setData
#5
execOrders
#6
0x59558d29
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x772ab420…c2f6
0x34b655…2a6f
4 touches
1 conflict
0x88e771e8…7d4a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x09a8bb29…b290
0x2ab50b…5c41
2 touches
0 conflicts
0x0c91d079…9552
0x2ab50b…5c41
2 touches
0 conflicts
0x0ca4d360…a141
0x2ab50b…5c41
2 touches
0 conflicts
0x0f8178c8…0ab7
0x2ab50b…5c41
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity