pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,086,406
← previous block
next block →
recent activity
Analyzing
Block #95,086,406
8 transactions · 8 stateful · 2026-08-11 14:34:25 UTC
Parallelism
63
/100
Blocked
50
%
Avg conflicts / tx
0.75
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,086,406
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOps
· blocks 2
#4
setData
#5
execOrders
· blocks 2
#2
execFwdPositionOps
· blocks 1
#6
execOrders
· blocks 1
#3
execFwdPositionOps
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xe9eb169f…a8be
0x34b655…2a6f
4 touches
1 conflict
0x3a62fa13…21ee
0x34b655…2a6f
4 touches
1 conflict
0x50e616e2…8782
0x34b655…2a6f
4 touches
1 conflict
0x57b02276…db3f
0x34b655…2a6f
4 touches
1 conflict
0x97f2226f…4561
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot
0x0000000000…0000c9
Audit this contract →
← previous block
·
next block →
recent activity