pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,155,096
← previous block
next block →
recent activity
Analyzing
Block #100,155,096
9 transactions · 8 stateful · 2026-08-29 10:01:19 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,155,096
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x5acec890
#3
execFwdPositionOpsV2
· blocks 1
#5
setData
#6
handleOps
#7
execFwdPositionOpsV2
#8
0x6a92ae67
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92fa1dc0…b239
0x34b655…2a6f
4 touches
1 conflict
0xa1472883…8ec1
0x34b655…2a6f
4 touches
1 conflict
0xb35e0bd9…84c1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x08f39e39…ed46
0x34b655…2a6f
4 touches
1 conflict
0x1a0e828a…c7ca
0x34b655…2a6f
4 touches
1 conflict
0x1a30dc9e…7931
0x34b655…2a6f
4 touches
1 conflict
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
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
0x92fa1dc002…a3b239
Audit this contract →
← previous block
·
next block →
recent activity