pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,555,324
← previous block
next block →
recent activity
Analyzing
Block #106,555,324
33 transactions · 28 stateful · 2026-09-20 20:11:56 UTC
Parallelism
70
/100
Blocked
75
%
Avg conflicts / tx
2.21
Longest chain
10
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,555,324
· 33 txs across 10 waves · depth 10
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
wave
w9
#0
syscallReward
#1
0x0c7abd22
· blocks 6
#4
execOrders
· blocks 6
#9
0x59558d29
· blocks 1
#11
0x59558d29
#13
execPerpOps
#14
execPerpOps
#17
forward
#18
0x57368ddf
#26
0x6ab03e10
#27
setData
#28
setData
#2
0x0c7abd22
· blocks 3
#5
execOrders
· blocks 9
#6
execOrders
· blocks 5
#10
0x59558d29
#19
execFwdPositionOpsV2
· blocks 2
#3
0x0c7abd22
#7
execOrders
· blocks 8
#20
execOrders
· blocks 3
#29
execOrders
· blocks 3
#8
0x3e2e8792
· blocks 7
#23
execOrders
· blocks 2
#30
execOrders
· blocks 2
#12
execOrders
· blocks 5
#16
execFwdPositionOpsV2
#31
execOrders
· blocks 1
#15
execFwdPositionOpsV2
· blocks 4
#32
execOrders
#21
execOrders
· blocks 3
#22
execOrders
· blocks 2
#24
execOrders
· blocks 1
#25
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w0
5
w1
6
w1
7
w2
8
w3
12
w4
15
w5
19
w1
20
w2
21
w6
22
w7
23
w3
24
w8
25
w9
29
w2
31
w4
32
w5
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03a6ea2e…2b49
0x34b655…2a6f
18 touches
36 conflicts
0xc53799eb…d928
0x34b655…2a6f
10 touches
10 conflicts
0xab41643c…f9bf
0x34b655…2a6f
10 touches
10 conflicts
0x86cea35b…bdff
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x04994ed2…9032
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot
0x03a6ea2ef2…442b49
Audit this contract →
← previous block
·
next block →
recent activity