pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,688,648
← previous block
next block →
recent activity
Analyzing
Block #92,688,648
11 transactions · 11 stateful · 2026-08-03 05:15:14 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,688,648
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
execFwdPositionOps
#3
forward
#5
0x6df9e92b
#6
execFwdPositionOps
#7
0x6a70245a
#8
setData
#9
0x59558d29
#10
0xc7e3ec2c
#4
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f00a5b3…bf76
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x083ff337…401b
0x34b655…2a6f
2 touches
0 conflicts
0x0b6b477f…e1bf
0x34b655…2a6f
2 touches
0 conflicts
0x1d1253eb…e0bd
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x286711a5…b3bf
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
0x1f00a5b37a…aebf76
Audit this contract →
← previous block
·
next block →
recent activity