pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,628,782
← previous block
next block →
recent activity
Analyzing
Block #100,628,782
12 transactions · 11 stateful · 2026-08-31 01:48:29 UTC
Parallelism
75
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,628,782
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x8263f5d9
#3
execOrders
#4
execOrders
· blocks 1
#5
execOrders
#8
0x57368ddf
#9
0x6a94dde4
#10
setData
#11
approve
#6
execOrders
· blocks 1
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba9f9225…2ead
0x34b655…2a6f
4 touches
1 conflict
0x6d5c5d72…914b
0x34b655…2a6f
4 touches
1 conflict
0x4690a385…779b
0x34b655…2a6f
4 touches
1 conflict
0x18e86f02…fa98
0x34b655…2a6f
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
2 touches
0 conflicts
0x29354600…7b17
0x34b655…2a6f
2 touches
0 conflicts
0x3055bfa7…ce68
0x34b655…2a6f
2 touches
0 conflicts
0x630da09a…093d
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
1 conflict on slot
0xba9f9225da…4d2ead
Audit this contract →
← previous block
·
next block →
recent activity