pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,820,803
← previous block
next block →
recent activity
Analyzing
Block #99,820,803
8 transactions · 7 stateful · 2026-08-28 05:56:44 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,820,803
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
#3
0x5acec890
#4
setData
#5
execFwdPositionOpsV2
· blocks 1
#7
execOrders
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4387ba94…e195
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x94a413b3…72e4
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0x62583b32…c1be
0x065c9d…c394
2 touches
0 conflicts
0xdb2e5132…9fad
0x065c9d…c394
2 touches
0 conflicts
0xf0ed54c3…c15c
0x065c9d…c394
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
0x4387ba941b…8be195
Audit this contract →
← previous block
·
next block →
recent activity