pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,583,807
← previous block
next block →
recent activity
Analyzing
Block #100,583,807
36 transactions · 28 stateful · 2026-08-30 22:02:13 UTC
Parallelism
72
/100
Blocked
61
%
Avg conflicts / tx
1.03
Longest chain
10
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,583,807
· 36 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
0xab083028
· blocks 3
#4
execOrders
#5
0x928e4afa
· blocks 5
#6
0xab083028
#7
0x32d01e04
#8
0x0c7abd22
· blocks 5
#13
0x59558d29
#14
0x9bcea3…9080
#15
0x02c3e1…17ba
#16
execPerpOps
#17
execPerpOps
#18
execOrders
#20
execPerpOps
#21
execOrders
#25
0x3f5c179b
#26
executeBatch
· blocks 1
#29
setData
#33
execOrders
#2
0x6ad2e98b
· blocks 2
#9
0x5acec890
· blocks 5
#22
execFwdPositionOpsV2
· blocks 2
#24
0x3f5c179b
#27
executeBatch
#3
0x6ad2e98b
· blocks 1
#10
0x5acec890
· blocks 1
#19
execOrders
#23
execFwdPositionOpsV2
· blocks 1
#11
0x5acec890
· blocks 2
#30
0xc7068c7b
#12
execOrder
· blocks 1
#28
execFwdPositionOpsV2
· blocks 2
#31
execOrders
· blocks 3
#32
execOrders
· blocks 2
#34
execOrders
· blocks 1
#35
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
5
w0
8
w0
9
w1
10
w2
11
w3
12
w4
19
w2
22
w1
24
w1
28
w5
30
w3
31
w6
32
w7
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x5f0a01c3…8269
0x851145…3f07
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe0f57943…818d
0x34b655…2a6f
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
6 conflicts on slot
0xac2a02739b…81721b
Audit this contract →
← previous block
·
next block →
recent activity