pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,561,524
← previous block
next block →
recent activity
Analyzing
Block #100,561,524
11 transactions · 10 stateful · 2026-08-30 20:10:08 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,561,524
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrder
#2
execOrder
#3
0x59558d29
#4
execFwdPositionOpsV2
· blocks 1
#5
transfer
#6
setData
#7
0x61d59c2d
#8
execOrders
· blocks 2
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w0
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xea57afd0…4232
0x34b655…2a6f
4 touches
1 conflict
0x452799ab…27d4
0x34b655…2a6f
2 touches
0 conflicts
0x45d2f27c…4c0b
0x34b655…2a6f
2 touches
0 conflicts
0x54b46054…b706
0x34b655…2a6f
2 touches
0 conflicts
0x6324ccc9…14fd
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity