pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,063,903
← previous block
next block →
recent activity
Analyzing
Block #100,063,903
10 transactions · 10 stateful · 2026-08-29 02:22:03 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,063,903
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
execOrders
· blocks 2
#3
0x59558d29
#5
execFwdPositionOpsV2
#7
transfer
#8
setData
#9
execOrders
#4
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99210cfe…f780
0x34b655…2a6f
6 touches
3 conflicts
0xf98c943e…7c44
0x34b655…2a6f
4 touches
1 conflict
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x007c19a0…3af4
0x34b655…2a6f
2 touches
0 conflicts
0x10b629c1…3ca7
0x34b655…2a6f
2 touches
0 conflicts
0x1d48c0e2…b62e
0x34b655…2a6f
2 touches
0 conflicts
0x24b08f9c…e594
0x34b655…2a6f
2 touches
0 conflicts
0x50c61506…343f
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
0x99210cfe0c…0df780
Audit this contract →
← previous block
·
next block →
recent activity