pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,114,496
← previous block
next block →
recent activity
Analyzing
Block #99,114,496
8 transactions · 8 stateful · 2026-08-25 18:29:18 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,114,496
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
0x59558d29
#4
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
#6
setData
#7
execOrders
#2
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc44d9a29…10e2
0x34b655…2a6f
4 touches
1 conflict
0xa02838a3…bc54
0x34b655…2a6f
4 touches
1 conflict
0x8f9aec0d…1b19
0x34b655…2a6f
4 touches
1 conflict
0x06c8fd5b…110f
0x34b655…2a6f
2 touches
0 conflicts
0x1c3c9acb…e2b0
0x34b655…2a6f
2 touches
0 conflicts
0x2965e2d6…5800
0x34b655…2a6f
2 touches
0 conflicts
0x454cdf57…aebc
0x34b655…2a6f
2 touches
0 conflicts
0x48717abe…be13
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
0xc44d9a29dc…1a10e2
Audit this contract →
← previous block
·
next block →
recent activity