pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,606,274
← previous block
next block →
recent activity
Analyzing
Block #99,606,274
9 transactions · 9 stateful · 2026-08-27 11:49:40 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,606,274
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x693c2be6
#2
execOrders
#3
0x5acec890
#4
0x59558d29
#5
setData
#6
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x014e90b3…470f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x75f6ea6f…ae4c
0x0a3323…0a3c
2 touches
0 conflicts
0x00000000…0010
0x4c8ebd…db3b
2 touches
0 conflicts
0xb96c6d7f…7166
0x4c8ebd…db3b
2 touches
0 conflicts
0xa060b594…669d
0x754704…b603
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity