pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,123,787
← previous block
next block →
recent activity
Analyzing
Block #95,123,787
9 transactions · 8 stateful · 2026-08-11 17:42:28 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,123,787
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#2
execOrder
· blocks 1
#4
execOrders
· blocks 1
#5
0x5acec890
#7
transfer
#8
setData
#3
execOrder
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2385516f…eca5
0x34b655…2a6f
4 touches
1 conflict
0xd9552b28…21e1
0x34b655…2a6f
4 touches
1 conflict
0xc139c876…fe04
0x34b655…2a6f
4 touches
1 conflict
0xe8eae8a3…bacc
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x4e8df67d…c10f
0x34b655…2a6f
2 touches
0 conflicts
0x5b1d7cdc…74c4
0x34b655…2a6f
2 touches
0 conflicts
0x745952b2…d90c
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
0x2385516f6a…9aeca5
Audit this contract →
← previous block
·
next block →
recent activity