pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,689,624
← previous block
next block →
recent activity
Analyzing
Block #92,689,624
18 transactions · 18 stateful · 2026-08-03 05:20:09 UTC
Parallelism
89
/100
Blocked
6
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,689,624
· 18 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
execFwdPositionOps
· blocks 1
#4
commit
#5
0x6a702581
#6
approve
#7
approve
#8
approve
#9
approve
#10
approve
#11
approve
#12
approve
#13
approve
#14
setData
#15
0x785f5745
#16
execOrders
#17
0xc7e3ec2c
#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
0xa6bb12cd…bf4a
0x34b655…2a6f
4 touches
1 conflict
0xe561281f…7569
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0cc5cf9a…310d
0x34b655…2a6f
2 touches
0 conflicts
0x1e04c5ec…8d51
0x34b655…2a6f
2 touches
0 conflicts
0x43898e28…3d30
0x34b655…2a6f
2 touches
0 conflicts
0x45340a67…d509
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
0xa6bb12cd3c…9fbf4a
Audit this contract →
← previous block
·
next block →
recent activity