pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,875,773
← previous block
next block →
recent activity
Analyzing
Block #99,875,773
9 transactions · 9 stateful · 2026-08-28 10:34:25 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,875,773
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
0x928e4afa
#3
execOrders
· blocks 2
#5
0x59558d29
#7
transferWithAuthorization
#8
setData
#4
execOrder
· blocks 1
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb856d1a1…1f18
0x34b655…2a6f
6 touches
3 conflicts
0x15413337…2a40
0x34b655…2a6f
6 touches
3 conflicts
0x2130a548…c1de
0x34b655…2a6f
4 touches
1 conflict
0x0ddb01d2…3beb
0x34b655…2a6f
2 touches
0 conflicts
0x2bcab7da…6268
0x34b655…2a6f
2 touches
0 conflicts
0x3507a867…9861
0x34b655…2a6f
2 touches
0 conflicts
0x3fff7ccd…5a48
0x34b655…2a6f
2 touches
0 conflicts
0x4b3b06fc…f6e2
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
3 conflicts on slot
0xb856d1a127…bf1f18
Audit this contract →
← previous block
·
next block →
recent activity