pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,020,417
← previous block
next block →
recent activity
Analyzing
Block #100,020,417
34 transactions · 30 stateful · 2026-08-28 22:43:10 UTC
Parallelism
76
/100
Blocked
57
%
Avg conflicts / tx
0.94
Longest chain
8
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,020,417
· 34 txs across 8 waves · depth 8
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
#0
syscallReward
#1
0xa96df62f
#2
0xab083028
· blocks 3
#4
0x5acec890
· blocks 6
#5
updatePrices
· blocks 2
#7
updatePrices
#12
updateDataFeedsValuesPartial
#13
execOrders
· blocks 1
#14
0x59558d29
#15
0x6a920f75
· blocks 1
#17
execFwdPositionOpsV2
#19
setData
#20
0x3f5c179b
#24
postStateList
#25
0x1dd53f…d6b0
#26
execOrders
#27
execOrders
#3
0xab083028
· blocks 2
#6
updatePrices
· blocks 1
#10
0x5acec890
· blocks 3
#16
0x6a920f76
#18
execFwdPositionOpsV2
#8
updatePrices
#9
0xab083028
· blocks 1
#11
0x5acec890
#21
0x3f5c179b
#23
execFwdPositionOpsV2
· blocks 1
#22
0x0c7abd22
· blocks 1
#28
execOrders
· blocks 4
#29
execOrders
· blocks 3
#33
0x0c7abd22
#30
execOrders
· blocks 2
#31
execOrders
· blocks 1
#32
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w0
6
w1
8
w2
9
w2
10
w1
11
w2
13
w0
15
w0
16
w1
18
w1
21
w2
22
w3
23
w2
28
w3
29
w4
30
w5
31
w6
32
w7
33
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xf8f1e808…a4fd
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x15698ac9…2a46
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 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
10 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity