pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,249,911
← previous block
next block →
recent activity
Analyzing
Block #99,249,911
11 transactions · 10 stateful · 2026-08-26 05:50:41 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,249,911
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
0x5acec890
#3
0x59558d29
#4
setData
#5
setData
#6
execFwdPositionOpsV2
#7
transfer
#8
0x6a8e7f29
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12e77486…ec2b
0x34b655…2a6f
2 touches
0 conflicts
0x1faeed20…190f
0x34b655…2a6f
2 touches
0 conflicts
0x2caeb7f5…b6bb
0x34b655…2a6f
2 touches
0 conflicts
0x556beb43…e627
0x34b655…2a6f
2 touches
0 conflicts
0x6d5d1fb5…86a7
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
0xe1c4e5ce15…770dec
Audit this contract →
← previous block
·
next block →
recent activity