pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,982,029
← previous block
next block →
recent activity
Analyzing
Block #100,982,029
11 transactions · 10 stateful · 2026-09-01 07:25:48 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,982,029
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
0x5acec890
· blocks 1
#5
0x59558d29
#6
redeem
#7
execFwdPositionOpsV2
#8
transferWithAuthorization
#9
setData
#4
0x5acec890
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8875810e…39f1
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x122f26cc…0b63
0x34b655…2a6f
2 touches
0 conflicts
0x198ff0c2…43dc
0x34b655…2a6f
2 touches
0 conflicts
0x1e81a9a0…46aa
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
0x8875810e04…a039f1
Audit this contract →
← previous block
·
next block →
recent activity